النمط المضاد للمصفوفة غير محدودة الحجم

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

Test your understanding of MongoDB & NoSQL Databases concepts from this lesson.

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.