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

Concept Flow - One-to-one embedding pattern

Start with main document

↓

Embed related document inside

↓

Store combined document in collection

↓

Query main document

↓

Access embedded document directly

↓

Update embedded document if needed

↓

End

This flow shows how a main document stores a related document inside it, enabling direct access and updates without separate collections.

Execution Sample

MongoDB

db.users.insertOne({
  _id: 1,
  name: "Alice",
  profile: { age: 30, city: "NY" }
})

Insert a user document with an embedded profile document inside it.

Execution Table

Step	Action	Document State	Result
1	Prepare main document with embedded profile	{ _id: 1, name: "Alice", profile: { age: 30, city: "NY" } }	Document ready to insert
2	Insert document into 'users' collection	Stored document in 'users'	Insertion successful
3	Query document by _id	Retrieved document with embedded profile	{ _id: 1, name: "Alice", profile: { age: 30, city: "NY" } }
4	Access embedded profile fields	profile.age = 30, profile.city = "NY"	Direct access without join
5	Update embedded profile city to "LA"	Updated document: { _id: 1, name: "Alice", profile: { age: 30, city: "LA" } }	Update successful
6	Query updated document	Retrieved updated document	{ _id: 1, name: "Alice", profile: { age: 30, city: "LA" } }
7	End	No further action	Process complete

💡 Process ends after document is inserted, queried, updated, and verified with embedded data.

Variable Tracker

Variable	Start	After Insert	After Update	Final
document	{}	{ _id: 1, name: "Alice", profile: { age: 30, city: "NY" } }	{ _id: 1, name: "Alice", profile: { age: 30, city: "LA" } }	{ _id: 1, name: "Alice", profile: { age: 30, city: "LA" } }

Key Moments - 2 Insights

Why do we embed the profile inside the user document instead of using a separate collection?

Embedding keeps related data together, so queries fetch all needed info in one go without joins, as shown in execution_table step 4.

How do we update the embedded profile city field?

We update the embedded field directly using dot notation, as shown in execution_table step 5, which modifies the city inside profile.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what is the value of profile.city?

A "LA"

B "NY"

C null

D "Chicago"

💡 Hint

Check the 'Document State' column at step 4 in execution_table.

At which step does the embedded profile city change to "LA"?

A Step 5

B Step 3

C Step 6

D Step 2

💡 Hint

Look for the update action in execution_table rows.

If we did not embed the profile, what would be a likely consequence?

A The document size would be smaller.

B The profile data would be faster to access.

C We would need to perform a join or multiple queries to get profile data.

D We could not update profile data.

💡 Hint

Refer to the concept_flow and key_moments about embedding benefits.

Concept Snapshot

One-to-one embedding pattern in MongoDB:
- Embed related document inside main document.
- Access embedded data directly without joins.
- Update embedded fields using dot notation.
- Best for tightly coupled data.
- Simplifies queries and improves read performance.

Full Transcript

The one-to-one embedding pattern in MongoDB means storing a related document inside a main document. For example, a user document can have a profile embedded inside it. This lets us fetch all data in one query without needing joins. We insert the combined document into a collection. When we query, we get the embedded document directly. We can update embedded fields using dot notation. This pattern is good when the related data is tightly connected and accessed together. It simplifies queries and improves performance by reducing the need for multiple queries.