El antipatrón de los arrays sin límite
Identificará cuándo la incrustación produce documentos que crecen sin límite y refactorizará el esquema para utilizar referencias en su lugar.
El antipatrón de los arrays sin límite es una lección gratuita de MongoDB Academy en CoddyKit. Esta es la lección 3 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de MongoDB Academy, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de MongoDB Academy incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
What Is an Unbounded Array?
An unbounded array is an array field inside a document that can grow indefinitely over time. If your schema design allows an array to accumulate items without any upper limit—like storing all user comments inside the user document, or all log entries inside an event document—you have an unbounded array anti-pattern. This is one of the most common MongoDB design mistakes.
The 16 MB Document Size Limit
MongoDB enforces a hard document size limit of 16 MB. An unbounded array grows that document over time. A user document that embeds all messages, all activity log entries, or all purchase history will eventually hit this ceiling. When the limit is reached, inserts fail with a BSONObjectTooLarge error, and there is no graceful way to recover without refactoring the schema.
Classic Anti-Pattern Example
Consider embedding all of a user's comments directly inside the user document. Each new comment pushes another element onto the comments array. An active user could write thousands of comments over months. This schema looks harmless at first but will grow the document without bound.
// ANTI-PATTERN: comments array grows forever
db.users.insertOne({
_id: ObjectId('u1'),
name: 'Alice',
comments: [
{ postId: ObjectId('p1'), text: 'Great article!', createdAt: new Date() },
{ postId: ObjectId('p2'), text: 'I disagree...', createdAt: new Date() }
// ... potentially thousands more
]
});Performance Degradation Before the Limit
Even before hitting 16 MB, large documents harm performance. MongoDB must read the entire document into memory for every operation, even if you only need one field. A user document with ten thousand embedded comments wastes RAM and I/O. Additionally, document growth triggers WiredTiger to move documents to new storage locations, causing fragmentation and write amplification.
Index Bloat From Unbounded Arrays
MongoDB creates a multikey index entry for every element in an indexed array. If you index comments.text on an array that grows to ten thousand elements, the index contains ten thousand entries per user. This bloats the index in memory and on disk, slowing down index scans across the entire collection.
Identifying the Anti-Pattern in Your Schema
Ask yourself these questions about any array field: (1) Can this array grow without a business-defined upper bound? (2) Is the data in this array primarily appended and rarely read all at once? (3) Would a single document with this array ever exceed a few kilobytes? If yes to any of these, you likely have an unbounded array that should be refactored.
Refactoring to a Separate Collection
The correct fix is to move the growing items into their own collection and store a reference. Each comment becomes its own document with a userId field pointing to the author. The user document stays lean and the comments collection can grow to billions of rows without any document hitting size limits.
// FIXED: comments live in their own collection
db.comments.insertMany([
{ _id: ObjectId(), userId: ObjectId('u1'), postId: ObjectId('p1'), text: 'Great article!', createdAt: new Date() },
{ _id: ObjectId(), userId: ObjectId('u1'), postId: ObjectId('p2'), text: 'I disagree...', createdAt: new Date() }
]);
// User document stays small
db.users.findOne({ _id: ObjectId('u1') }); // no comments arrayThe Bucket Pattern as an Alternative
Sometimes you still want to group related events together for efficiency—for example, hourly IoT sensor readings. The bucket pattern creates one document per time bucket (e.g., one per hour) with an embedded array of readings for that period. Each bucket is bounded by the time window, so no single document grows unboundedly. This pattern is common in time-series and analytics schemas.
// Bucket pattern: one document per device per hour
db.sensorReadings.insertOne({
deviceId: 'sensor-42',
bucketStart: new Date('2024-01-01T09:00:00Z'),
readings: [
{ ts: new Date('2024-01-01T09:00:10Z'), temp: 22.1 },
{ ts: new Date('2024-01-01T09:00:20Z'), temp: 22.3 }
// bounded to at most ~60 readings per hour bucket
],
count: 2
});Limiting Array Size With Application Logic
Another approach for capped use cases—like showing the last 5 notifications—is to use $push with $slice to keep the array at a fixed maximum length. This way the array never grows beyond a known size. This is acceptable when only the most recent N items matter and older items can be discarded.
// Keep only the 5 most recent notifications
db.users.updateOne(
{ _id: ObjectId('u1') },
{
$push: {
notifications: {
$each: [{ message: 'New follower', createdAt: new Date() }],
$slice: -5 // retain only the last 5 elements
}
}
}
);Detecting Large Documents in Production
To find documents approaching the size limit in a live collection, use the aggregation pipeline with $bsonSize (MongoDB 4.4+). This expression returns the size of a document in bytes, allowing you to identify and prioritise schema refactoring before a production failure occurs.
// Find documents larger than 1 MB in the users collection
db.users.aggregate([
{
$project: {
name: 1,
docSize: { $bsonSize: '$$ROOT' }
}
},
{ $match: { docSize: { $gt: 1048576 } } }, // 1 MB
{ $sort: { docSize: -1 } }
]);Choosing the Right Refactoring Strategy
When you identify an unbounded array, choose your refactoring strategy based on the data's nature:
- Separate collection + reference: for data that needs independent queries or could grow to thousands of items
- Bucket pattern: for time-ordered events grouped by a natural time window
- $push + $slice: for capped recent-items lists where old data can be dropped
Quick Check
Test your understanding of MongoDB & NoSQL Databases concepts from this lesson.
Lesson Recap
In this lesson you learned: unbounded arrays grow documents past the 16 MB limit, large embedded arrays cause memory waste, index bloat, and write amplification, and solutions include separate collections, the bucket pattern, or capped arrays with $slice. Next up we build a schema design decision framework to choose embedding or referencing systematically.
Preguntas frecuentes
¿La lección «El antipatrón de los arrays sin límite» es gratis?
Sí — el texto completo de «El antipatrón de los arrays sin límite» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de MongoDB Academy, actualiza a CoddyKit PRO. El curso de MongoDB Academy incluye 4 lecciones en total.
¿Qué aprenderé en «El antipatrón de los arrays sin límite»?
Identificará cuándo la incrustación produce documentos que crecen sin límite y refactorizará el esquema para utilizar referencias en su lugar. Practicas MongoDB Academy con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar MongoDB Academy?
No se requiere experiencia previa. MongoDB Academy en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 3 de 4.
¿Cuánto tiempo toma la lección «El antipatrón de los arrays sin límite»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de MongoDB Academy?
Sí. Cada lección de MongoDB Academy incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Incrustación: relaciones de uno a pocos
- Referencias: relaciones de uno a muchos y de muchos a muchos
- El antipatrón de los arrays sin límite
- Marco de decisión para diseñar esquemas