Why document design matters in MongoDB - See It in Action

Why Document Design Matters in MongoDB

📖 Scenario: You are working for a small online bookstore. You want to store information about books and their authors in a MongoDB database. Good document design will help you store and retrieve data efficiently.

🎯 Goal: Build a MongoDB collection with well-designed documents that store book titles, authors, and publication years. Learn how to structure documents for easy querying and updating.

📋 What You'll Learn

Create a collection called books with documents containing title, author, and year fields.

Add a configuration variable maxYear to filter books published after this year.

Write a query to find all books published after maxYear.

Add an index on the year field to improve query performance.

💡 Why This Matters

🌍 Real World

Good document design helps online stores and apps store and retrieve data quickly and clearly.

💼 Career

Database developers and data engineers must design documents and indexes to optimize performance and maintainability.

1

Create the books collection with initial documents

Create a MongoDB collection called books and insert these exact documents: { title: "The Great Gatsby", author: "F. Scott Fitzgerald", year: 1925 }, { title: "1984", author: "George Orwell", year: 1949 }, and { title: "To Kill a Mockingbird", author: "Harper Lee", year: 1960 }.

MongoDB

// Insert the three book documents into the books collection
// Your code here

Hint

Use insertMany to add multiple documents to the books collection.

2

Add a configuration variable maxYear

Create a variable called maxYear and set it to 1930. This will be used to filter books published after this year.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", year: 1925 },
  { title: "1984", author: "George Orwell", year: 1949 },
  { title: "To Kill a Mockingbird", author: "Harper Lee", year: 1960 }
])

// Create maxYear variable
// Your code here

Hint

Use const maxYear = 1930 to create the variable.

3

Query books published after maxYear

Write a MongoDB query using find on the books collection to get all documents where the year field is greater than maxYear. Store the query in a variable called recentBooks.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", year: 1925 },
  { title: "1984", author: "George Orwell", year: 1949 },
  { title: "To Kill a Mockingbird", author: "Harper Lee", year: 1960 }
])

const maxYear = 1930

// Query books with year > maxYear
// Your code here

Hint

Use db.books.find({ year: { $gt: maxYear } }) to get books published after maxYear.

4

Add an index on the year field

Create an index on the year field of the books collection using createIndex to improve query speed.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", year: 1925 },
  { title: "1984", author: "George Orwell", year: 1949 },
  { title: "To Kill a Mockingbird", author: "Harper Lee", year: 1960 }
])

const maxYear = 1930

const recentBooks = db.books.find({ year: { $gt: maxYear } })

// Create an index on the year field
// Your code here

Hint

Use db.books.createIndex({ year: 1 }) to create an ascending index on the year field.

Practice

1. Why is good document design important in MongoDB?

easy

A. It groups related data together for faster access.

B. It makes the database use more disk space.

C. It forces all data to be stored in separate collections.

D. It prevents any data from being updated.

Solution

1. Step 1: Understand document design purpose

   Good document design groups related data to reduce the number of database lookups.

2. Step 2: Identify the benefit of grouping data

   Grouping related data together makes data access faster and simpler for the application.

3. Final Answer:

   It groups related data together for faster access. -> Option A

4. Quick Check:

   Good design = grouped data = faster access [OK]

Hint: Good design groups related data for speed [OK]

Common Mistakes:

• Thinking design increases disk space unnecessarily
• Believing all data must be in separate collections
• Assuming design stops data updates

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

easy

A. { name: 'Alice', address: ['NY', '10001'] }

B. { name: 'Alice', address: { city: 'NY', zip: '10001' } }

C. { name: 'Alice', address: 'NY, 10001' }

D. { name: 'Alice', address: null }

Solution

1. Step 1: Recognize embedded document syntax

   Embedding means putting a document inside another document as a nested object.

2. Step 2: Identify correct nested object format

   { name: 'Alice', address: { city: 'NY', zip: '10001' } } uses a nested object with keys city and zip, which is correct for embedding.

3. Final Answer:

   { name: 'Alice', address: { city: 'NY', zip: '10001' } } -> Option B

4. Quick Check:

   Embedded document = nested object = { name: 'Alice', address: { city: 'NY', zip: '10001' } } [OK]

Hint: Embed data as nested objects, not arrays or strings [OK]

Common Mistakes:

• Using arrays instead of objects for embedded data
• Storing address as a plain string
• Leaving embedded fields null without reason

3. Given this user document:
{ _id: 1, name: 'Bob', orders: [{ id: 101, total: 50 }, { id: 102, total: 30 }] }
What will be the result of the query db.users.findOne({ _id: 1 })?

medium

A. null

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

C. { _id: 1, name: 'Bob', orders: [{ id: 101, total: 50 }, { id: 102, total: 30 }] }

D. SyntaxError

Solution

1. Step 1: Understand findOne query behavior

   The findOne query returns the entire document matching the filter {_id: 1}.

2. Step 2: Check document structure

   The document includes the orders array embedded inside, so the full document is returned.

3. Final Answer:

   { _id: 1, name: 'Bob', orders: [{ id: 101, total: 50 }, { id: 102, total: 30 }] } -> Option C

4. Quick Check:

   findOne returns full document = { _id: 1, name: 'Bob', orders: [{ id: 101, total: 50 }, { id: 102, total: 30 }] } [OK]

Hint: findOne returns full matching document [OK]

Common Mistakes:

• Expecting only part of the document returned
• Thinking query returns null if embedded arrays exist
• Confusing syntax errors with valid queries

4. You want to embed a list of comments inside a blog post document, but your code throws an error. Which is the likely cause?
{ title: 'Post', comments: 'Great post!' }

medium

A. Comments should be an array of objects, not a string.

B. Title field cannot be a string.

C. MongoDB does not allow embedding arrays.

D. The document must have an _id field.

Solution

1. Step 1: Check the comments field type

   Comments are given as a string, but embedding multiple comments requires an array of objects.

2. Step 2: Understand embedding requirements

   Embedding multiple related items means using an array of objects, not a single string.

3. Final Answer:

   Comments should be an array of objects, not a string. -> Option A

4. Quick Check:

   Embed lists as arrays, not strings [OK]

Hint: Embed lists as arrays of objects, not strings [OK]

Common Mistakes:

• Using string instead of array for multiple items
• Thinking title cannot be string
• Believing MongoDB forbids arrays
• Assuming _id is always required manually

5. You have a product catalog where each product has many reviews. Reviews can grow large over time. What is the best document design to handle this efficiently?

hard

A. Embed all reviews inside each product document.

B. Duplicate product data inside each review document.

C. Store only the first review inside the product document.

D. Store reviews in a separate collection linked by product ID.

Solution

1. Step 1: Consider document size limits and growth

   Embedding many reviews inside a product can make the document very large and slow to update.

2. Step 2: Choose design for large growing data

   Storing reviews separately and linking by product ID keeps product documents small and queries efficient.

3. Final Answer:

   Store reviews in a separate collection linked by product ID. -> Option D

4. Quick Check:

   Large growing data = separate collection [OK]

Hint: Large growing lists? Use separate collections [OK]

Common Mistakes:

• Embedding large growing arrays inside documents
• Storing only partial data inside main document
• Duplicating product data unnecessarily