MongoDB Academy · 课时

无界数组反模式

您将识别嵌入何时会导致文档无限增长，并重构模式，改用引用。

无界数组反模式 是 CoddyKit 上的免费 MongoDB Academy 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 MongoDB Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 MongoDB Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

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 array

The 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

All three prevent document bloat, but each suits a different access pattern.

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.

常见问题解答

「无界数组反模式」课时是免费的吗？

是的 — 「无界数组反模式」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 MongoDB Academy 课程的其余内容，请升级到 CoddyKit PRO。 MongoDB Academy 课程共包含 4 节课。

「无界数组反模式」这节课中我会学到什么？

您将识别嵌入何时会导致文档无限增长，并重构模式，改用引用。你通过在浏览器中直接运行的动手代码来练习 MongoDB Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 MongoDB Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 MongoDB Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「无界数组反模式」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 MongoDB Academy 课中编写并运行代码吗？

能。每节 MongoDB Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 MongoDB Academy