mongodb-schema-and-indexing

MongoDB Schema Design & Indexing Optimization Guide

Comprehensive architectural reference for MongoDB schema modeling, high-performance indexing, aggregation pipeline tuning, and cluster sharding strategies.

---

1. Schema Modeling Framework: Embedding vs. Referencing

Decision Matrix

                      Do entities have a 1:1 or 1:Few relationship?
                                     /             \
                                  YES               NO
                                  /                   \
           Embed data inside parent document         Do child documents grow unbounded?
                                                            /             \
                                                         YES               NO
                                                         /                   \
                                            Use Two-Way Referencing      Embed with Subset Pattern

Factor	Embedded Subdocuments	Referenced Documents (Normalized)
Query Performance	Fast ($O(1)$ single read, no joins)	Requires $lookup or application-side joins
Atomicity	Atomic updates across whole document	Requires Multi-Document Transactions (session)
Document Size Limit	Subject to 16 MB BSON hard limit	Multi-document architecture bypasses limit
Data Redundancy	Possible duplication across documents	Single source of truth

---

2. Advanced MongoDB Design Patterns

2.1 Subset Pattern

• Problem: Large embedded array (e.g., 5,000 product reviews) causes huge document size and slow memory loading.
• Solution: Keep only the 10 most recent reviews in the main product document; store all historical reviews in a separate reviews collection.

2.2 Extended Reference Pattern

• Problem: Frequent joins ($lookup) just to fetch 1 or 2 fields (e.g., customerName and customerEmail on an Order).
• Solution: Copy immutable or rarely changed target fields directly into the order document:

  {
    "_id": ObjectId("6697a4..."),
    "totalAmount": 149.99,
    "customer": {
      "id": ObjectId("6697a2..."),
      "name": "Jane Doe",
      "email": "[email protected]"
    }
  }