Normalization vs denormalization default in MongoDB - Visual Side-by-Side Comparison

Concept Flow - Normalization vs denormalization default

Start: Data Storage

↓

Normalization

↓

Separate Collections

↓

Use References

↓

Join Data at Query

↓

More Queries

↓

Less Data Duplication

↓

Complex Updates

↓

End

This flow shows the choice between normalization and denormalization in MongoDB, highlighting how data is stored, queried, and updated differently.

Execution Sample

MongoDB

db.orders.insertOne({
  _id: 1,
  customer: { _id: 101, name: "Alice" },
  items: [ { product: "Pen", qty: 3 } ]
})

Insert an order document embedding customer info and items, showing denormalization by embedding related data.

Execution Table

Step	Action	Data Structure	Query Type	Effect
1	Insert order with embedded customer	Order document with embedded customer object	Insert	Data stored in one document, no references
2	Query order by _id	Single document with embedded data	FindOne	Single query returns order and customer info
3	Update customer name	Customer data inside order document	Update	Must update all orders embedding this customer
4	Insert order with customer reference	Order document with customer _id reference	Insert	Data split across collections
5	Query order and join customer	Order references customer collection	Aggregate with $lookup	Multiple queries combined, more complex
6	Update customer name in customer collection	Customer data centralized	Update	Single update affects all orders referencing customer
7	End	-	-	Shows trade-offs between normalization and denormalization

💡 Process ends after showing key steps of data insertion, querying, and updating in both models.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	After Step 6	Final
Order Document	Empty	{_id:1, customer:{_id:101, name:"Alice"}, items:[...]}	{_id:1, customer:{_id:101, name:"Alice B."}, items:[...]}	{_id:2, customer_id:101, items:[...]}	{_id:2, customer_id:101, items:[...]}	Shows embedded and referenced forms
Customer Data	Empty	Embedded in order	Embedded updated in all orders	Separate collection	Updated once centrally	Centralized customer data

Key Moments - 3 Insights

Why do we need to update multiple documents when customer data is embedded?

Because in denormalization, customer info is copied inside each order document (see execution_table step 3), so each order must be updated to keep data consistent.

How does referencing customer data simplify updates?

Referencing stores customer data in one place (execution_table step 6), so updating customer info once updates all related orders automatically.

Why does querying become more complex with normalization?

Because data is split across collections and requires joins or $lookup (execution_table step 5), needing multiple queries combined.

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what data is returned by the query?

A Order data with embedded customer info

B Customer data only

C Only order data without customer info

D No data returned

💡 Hint

Check the 'Data Structure' column at step 2 showing embedded customer object.

At which step does updating customer data require changing multiple documents?

A Step 1

B Step 6

C Step 3

D Step 5

💡 Hint

Look at 'Effect' column in step 3 about updating embedded customer data.

If we embed customer data in orders, how does it affect query complexity?

A Queries require more joins

B Queries become simpler with fewer joins

C Queries need aggregation pipelines

D Queries cannot find customer data

💡 Hint

Refer to execution_table step 2 vs step 5 comparing embedded vs referenced queries.

Concept Snapshot

Normalization vs Denormalization in MongoDB:
- Normalization: store related data in separate collections using references.
- Denormalization: embed related data inside documents.
- Normalization reduces data duplication but needs joins ($lookup).
- Denormalization simplifies queries but duplicates data.
- Choose based on update frequency and query needs.

Full Transcript

This visual execution shows how MongoDB handles data with normalization and denormalization. Normalization stores related data in separate collections and uses references, requiring joins during queries but simplifying updates. Denormalization embeds related data inside documents, making queries simpler but requiring updates in multiple places. The execution table traces inserting orders with embedded customer data versus referencing customer data, querying them, and updating customer info. Variable tracking shows how order and customer data change. Key moments clarify why updates differ and how query complexity changes. The quiz tests understanding of these trade-offs. This helps beginners see practical effects of data modeling choices in MongoDB.

Practice

1. What is the main advantage of normalization in MongoDB databases?

easy

A. It separates data into collections linked by references for easy updates.

B. It stores all related data together in one document for faster reads.

C. It duplicates data to improve write performance.

D. It automatically creates indexes on all fields.

Solution

1. Step 1: Understand normalization concept

   Normalization means splitting data into separate collections and linking them by references.

2. Step 2: Identify the main benefit

   This separation makes updating data easier because changes happen in one place without duplication.

3. Final Answer:

   It separates data into collections linked by references for easy updates. -> Option A

4. Quick Check:

   Normalization = separate collections + easy updates [OK]

Hint: Normalization means separate collections linked by references [OK]

Common Mistakes:

• Confusing normalization with denormalization
• Thinking normalization duplicates data
• Assuming normalization speeds up reads

2. Which MongoDB document structure shows denormalization?

easy

A. { _id: 1, name: 'Alice' }, { _id: 101, userId: 1, item: 'Book' }

B. { _id: 1, name: 'Alice', orders: [ { orderId: 101, item: 'Book' } ] }

C. { _id: 101, userId: 1, item: 'Book' }

D. { _id: 1, name: 'Alice', orders: null }

Solution

1. Step 1: Identify denormalized structure

   Denormalization stores related data together inside one document, like embedding orders inside user.

2. Step 2: Check options for embedded data

   { _id: 1, name: 'Alice', orders: [ { orderId: 101, item: 'Book' } ] } embeds orders array inside the user document, showing denormalization.

3. Final Answer:

   { _id: 1, name: 'Alice', orders: [ { orderId: 101, item: 'Book' } ] } -> Option B

4. Quick Check:

   Denormalization = embedded related data [OK]

Hint: Denormalization embeds related data inside one document [OK]

Common Mistakes:

• Choosing separate collections as denormalized
• Ignoring embedded arrays as denormalization
• Confusing null fields with embedded data

3. Given these two collections:
users: { _id: 1, name: 'Bob' }
orders: { _id: 101, userId: 1, item: 'Pen' }
What is the main drawback of this normalized design when reading user orders?

medium

A. It requires multiple queries or a join-like operation to get all orders for a user.

B. It duplicates order data inside each user document.

C. It stores all orders inside the user document causing large documents.

D. It prevents updating user names easily.

Solution

1. Step 1: Understand normalized design

   Users and orders are in separate collections linked by userId reference.

2. Step 2: Identify drawback when reading

   To get all orders for a user, you must query orders collection filtering by userId, requiring multiple queries or aggregation.

3. Final Answer:

   It requires multiple queries or a join-like operation to get all orders for a user. -> Option A

4. Quick Check:

   Normalized read = multiple queries [OK]

Hint: Normalized data needs multiple queries to combine related info [OK]

Common Mistakes:

• Thinking normalized data duplicates info
• Assuming all data is embedded in one document
• Believing updates are harder in normalized data

4. You have a denormalized MongoDB document:
{ _id: 1, name: 'Carol', orders: [ { orderId: 201, item: 'Notebook' } ] }
Which problem can occur if you update the item name in one order but forget to update it elsewhere?

medium

A. Query performance slows down because of references.

B. Indexes on orders array are lost.

C. The database schema becomes normalized automatically.

D. Data inconsistency due to duplicated order info in multiple documents.

Solution

1. Step 1: Recognize denormalization risk

   Denormalization duplicates related data inside documents, so the same order info may appear in many places.

2. Step 2: Understand update problem

   If you update one copy but not others, data becomes inconsistent and unreliable.

3. Final Answer:

   Data inconsistency due to duplicated order info in multiple documents. -> Option D

4. Quick Check:

   Denormalization risk = data inconsistency [OK]

Hint: Denormalization can cause inconsistent duplicated data if not updated everywhere [OK]

Common Mistakes:

• Thinking denormalization slows queries
• Believing schema changes automatically
• Confusing index loss with denormalization

5. You want to design a MongoDB schema for a blog with users and posts.
Users have many posts, and posts rarely change after creation.
Which design is best for fast reading and why?

Options:
A: Store users and posts in separate collections (normalized).
B: Embed all posts inside each user document (denormalized).
C: Duplicate posts in both users and posts collections.
D: Store posts only, with user info duplicated in each post.

hard

A. Separate collections for users and posts for easy updates.

B. Store posts only with duplicated user info for simpler queries.

C. Embed posts inside user documents for fast reads since posts rarely change.

D. Duplicate posts in both collections to optimize writes.

Solution

1. Step 1: Analyze data change frequency

   Posts rarely change, so embedding them inside users won't cause frequent update problems.

2. Step 2: Choose design for fast reads

   Embedding posts inside user documents allows fetching user and posts in one read, improving read speed.

3. Step 3: Compare options

   Embedding posts inside user documents for fast reads since posts rarely change fits best for fast reads with rare updates; separate collections require joins; duplicating posts in both risks inconsistency; storing posts only duplicates user info unnecessarily.

4. Final Answer:

   Embed posts inside user documents for fast reads since posts rarely change. -> Option C

5. Quick Check:

   Denormalization + rare updates = embed for fast reads [OK]

Hint: Embed rarely changing related data for faster reads [OK]

Common Mistakes:

• Choosing normalization for fast reads
• Duplicating data causing inconsistency
• Ignoring update frequency in design