One-to-many embedding pattern in MongoDB - Step-by-Step Execution

Concept Flow - One-to-many embedding pattern

Start with main document

↓

Embed array of related documents

↓

Store all data in one document

↓

Query main document with embedded array

↓

Access embedded documents directly

↓

Update embedded documents as needed

↓

End

This flow shows how a main document contains an array of embedded related documents, allowing direct access and updates within a single document.

Execution Sample

MongoDB

db.authors.insertOne({
  name: "Alice",
  books: [
    { title: "Book A", year: 2020 },
    { title: "Book B", year: 2022 }
  ]
})

Insert an author document with an embedded array of book documents.

Execution Table

Step	Action	Document State	Result
1	Prepare author document with embedded books array	{ name: "Alice", books: [{title: "Book A", year: 2020}, {title: "Book B", year: 2022}] }	Document ready for insertion
2	Insert document into 'authors' collection	N/A	Document inserted with _id assigned
3	Query author by name	N/A	Returns document with embedded books array
4	Access embedded books array	{ books: [...] }	Can read all embedded book documents directly
5	Update year of 'Book A' to 2021	N/A	Embedded document updated inside main document
6	Query updated author document	N/A	Returns document with updated embedded book year
7	End of operation	N/A	Process complete

💡 All operations complete; embedded documents accessed and updated within main document.

Variable Tracker

Variable	Start	After Insert	After Update	Final
authorDocument	{}	{ name: "Alice", books: [{title: "Book A", year: 2020}, {title: "Book B", year: 2022}] }	{ name: "Alice", books: [{title: "Book A", year: 2021}, {title: "Book B", year: 2022}] }	{ name: "Alice", books: [{title: "Book A", year: 2021}, {title: "Book B", year: 2022}] }

Key Moments - 2 Insights

Why do we embed the books inside the author document instead of using separate collections?

Embedding keeps related data together, so when you query the author, you get all their books at once without extra queries, as shown in execution_table step 3 and 4.

How do we update a specific embedded book's field?

You update the embedded document inside the main document, as in step 5, by targeting the array element and changing its field directly.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what data structure holds the books?

A A separate collection linked by author ID

B An embedded array inside the author document

C A flat list outside the author document

D A single book document only

💡 Hint

Check the 'Document State' column at step 4 showing books inside the author document.

At which step does the embedded book's year get updated?

A Step 3

B Step 2

C Step 5

D Step 6

💡 Hint

Look at the 'Action' column describing the update operation.

If we added a new book to the embedded array, which step would be similar to that operation?

A Step 5 - updating an embedded document

B Step 3 - querying the document

C Step 1 - preparing the document

D Step 7 - end of operation

💡 Hint

Adding a book is like updating the embedded array, similar to the update in step 5.

Concept Snapshot

One-to-many embedding pattern:
- Store related many documents inside one main document as an array.
- Query returns main document with all embedded data.
- Update embedded documents directly inside main document.
- Good for data accessed together, avoids joins.
- Use when embedded data size is manageable.

Full Transcript

The one-to-many embedding pattern in MongoDB means putting many related items inside one main document as an array. For example, an author document can have an array of book documents inside it. This way, when you get the author, you get all their books at once. You can also update any embedded book directly inside the author document. This pattern is good when you want to keep related data together and avoid multiple queries. The example shows inserting an author with two books, querying the author, and updating a book's year inside the embedded array.