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.

Practice

1. What is the main advantage of using the one-to-one embedding pattern in MongoDB?

easy

A. It requires complex joins to retrieve related data.

B. It splits data into multiple collections to reduce document size.

C. It stores related data inside a single document for faster reads.

D. It duplicates data across collections for backup.

Solution

1. Step 1: Understand one-to-one embedding

   One-to-one embedding stores related data inside the same document instead of separate collections.

2. Step 2: Identify the advantage

   This approach simplifies queries and improves read speed by avoiding joins.

3. Final Answer:

   It stores related data inside a single document for faster reads. -> Option C

4. Quick Check:

   Embedding = faster reads [OK]

Hint: Embedding keeps related data together for quick access [OK]

Common Mistakes:

• Thinking embedding splits data into multiple collections
• Assuming embedding requires joins
• Confusing embedding with data duplication

2. Which of the following is the correct way to embed a profile document inside a user document in MongoDB?

easy

A. { _id: 1, name: 'Alice' }, profile: { age: 30, city: 'NY' }

B. { _id: 1, name: 'Alice', profile: { age: 30, city: 'NY' } }

C. { _id: 1, name: 'Alice', profile: [ { age: 30, city: 'NY' } ] }

D. { _id: 1, name: 'Alice', profile: 'age:30, city:NY' }

Solution

1. Step 1: Check embedding syntax

   Embedding means nesting a document inside another document as a field with an object value.

2. Step 2: Identify correct JSON structure

   { _id: 1, name: 'Alice', profile: { age: 30, city: 'NY' } } correctly nests the profile as an object inside user. { _id: 1, name: 'Alice' }, profile: { age: 30, city: 'NY' } separates profile outside user. { _id: 1, name: 'Alice', profile: [ { age: 30, city: 'NY' } ] } uses an array unnecessarily. { _id: 1, name: 'Alice', profile: 'age:30, city:NY' } stores profile as a string, not an object.

3. Final Answer:

   { _id: 1, name: 'Alice', profile: { age: 30, city: 'NY' } } -> Option B

4. Quick Check:

   Embedded document = nested object [OK]

Hint: Embed as nested object, not separate or string [OK]

Common Mistakes:

• Placing embedded document outside main document
• Using array instead of object for one-to-one
• Storing embedded data as string

3. Given the document { _id: 1, name: 'Bob', address: { street: 'Main St', city: 'LA' } }, what will be the result of the query db.users.findOne({ _id: 1 })?

medium

A. { _id: 1, name: 'Bob' }

B. null

C. { address: { street: 'Main St', city: 'LA' } }

D. { _id: 1, name: 'Bob', address: { street: 'Main St', city: 'LA' } }

Solution

1. Step 1: Understand findOne query

   The query searches for a document with _id equal to 1 and returns the whole document.

2. Step 2: Check document structure

   The document includes embedded address inside user, so the full document is returned.

3. Final Answer:

   { _id: 1, name: 'Bob', address: { street: 'Main St', city: 'LA' } } -> Option D

4. Quick Check:

   findOne returns full document [OK]

Hint: findOne returns entire matching document including embedded [OK]

Common Mistakes:

• Expecting only top-level fields returned
• Thinking embedded fields are separate documents
• Assuming query returns null if embedded exists

4. You have this document: { _id: 2, name: 'Carol', profile: { age: 25, city: 'Chicago' } }. Which update command correctly changes the city to 'Boston' using one-to-one embedding?

medium

A. db.users.updateOne({ _id: 2 }, { $set: { 'profile.city': 'Boston' } })

B. db.users.updateOne({ _id: 2 }, { $set: { profile: 'Boston' } })

C. db.users.updateOne({ _id: 2 }, { $set: { city: 'Boston' } })

D. db.users.updateOne({ _id: 2 }, { $set: { 'profile[city]': 'Boston' } })

Solution

1. Step 1: Identify correct update syntax for embedded field

   To update a nested field, use dot notation like 'profile.city'.

2. Step 2: Check each option

   db.users.updateOne({ _id: 2 }, { $set: { 'profile.city': 'Boston' } }) uses correct dot notation. db.users.updateOne({ _id: 2 }, { $set: { profile: 'Boston' } }) replaces entire profile with string. db.users.updateOne({ _id: 2 }, { $set: { city: 'Boston' } }) tries to set city at top level, which doesn't exist. db.users.updateOne({ _id: 2 }, { $set: { 'profile[city]': 'Boston' } }) uses invalid bracket notation.

3. Final Answer:

   db.users.updateOne({ _id: 2 }, { $set: { 'profile.city': 'Boston' } }) -> Option A

4. Quick Check:

   Use dot notation to update embedded fields [OK]

Hint: Use dot notation to update embedded fields [OK]

Common Mistakes:

• Replacing whole embedded document instead of one field
• Using incorrect field path without dot notation
• Using invalid bracket notation in update

5. You want to design a MongoDB schema for users and their passports using one-to-one embedding. Which design is best and why?

hard

A. Embed passport details inside user document because passports are small and tightly linked.

B. Store passports in a separate collection and reference user IDs to avoid large documents.

C. Duplicate passport data in both user and passport collections for faster writes.

D. Store passport as a string field inside user document to simplify queries.

Solution

1. Step 1: Analyze data relationship and size

   Passports are small and tightly connected to users, perfect for embedding.

2. Step 2: Choose embedding benefits

   Embedding keeps related data together, simplifies queries, and improves read speed.

3. Step 3: Evaluate other options

   Store passports in a separate collection and reference user IDs to avoid large documents adds complexity with references. Duplicate passport data in both user and passport collections for faster writes duplicates data causing inconsistency. Store passport as a string field inside user document to simplify queries stores data as string losing structure.

4. Final Answer:

   Embed passport details inside user document because passports are small and tightly linked. -> Option A

5. Quick Check:

   Small, tightly linked data = embed [OK]

Hint: Embed small, tightly linked data for simplicity and speed [OK]

Common Mistakes:

• Choosing references for small one-to-one data
• Duplicating data causing inconsistency
• Storing structured data as plain string