Why query patterns matter in MongoDB - See It in Action

Why Query Patterns Matter in MongoDB

📖 Scenario: You are managing a small online bookstore database using MongoDB. You want to understand how different query patterns affect the speed and efficiency of finding books.

🎯 Goal: Build a simple MongoDB collection with book data, add an index, and write queries to see how query patterns impact performance.

📋 What You'll Learn

Create a MongoDB collection called books with specific book documents

Add an index on the author field

Write a query to find books by a specific author

Write a query to find books by a specific author and genre

💡 Why This Matters

🌍 Real World

Online bookstores and many apps use databases like MongoDB to store and find data quickly. Understanding query patterns helps keep the app fast.

💼 Career

Database developers and backend engineers must write efficient queries and create indexes to optimize data retrieval in real projects.

1

Create the books collection with sample data

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

MongoDB

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

Hint

Use db.books.insertMany() with an array of book objects.

2

Add an index on the author field

Create an index on the author field in the books collection using db.books.createIndex.

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", genre: "Classic" },
  { title: "1984", author: "George Orwell", genre: "Dystopian" },
  { title: "To Kill a Mockingbird", author: "Harper Lee", genre: "Classic" }
])
// Create an index on the author field
// Your code here

Hint

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

3

Write a query to find books by author

Write a query using db.books.find to find all books where the author is exactly "George Orwell".

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", genre: "Classic" },
  { title: "1984", author: "George Orwell", genre: "Dystopian" },
  { title: "To Kill a Mockingbird", author: "Harper Lee", genre: "Classic" }
])
db.books.createIndex({ author: 1 })
// Find books by author "George Orwell"
// Your code here

Hint

Use db.books.find({ author: "George Orwell" }) to get books by that author.

4

Write a query to find books by author and genre

Write a query using db.books.find to find all books where the author is "Harper Lee" and the genre is "Classic".

MongoDB

db.books.insertMany([
  { title: "The Great Gatsby", author: "F. Scott Fitzgerald", genre: "Classic" },
  { title: "1984", author: "George Orwell", genre: "Dystopian" },
  { title: "To Kill a Mockingbird", author: "Harper Lee", genre: "Classic" }
])
db.books.createIndex({ author: 1 })
db.books.find({ author: "George Orwell" })
// Find books by author "Harper Lee" and genre "Classic"
// Your code here

Hint

Use db.books.find({ author: "Harper Lee", genre: "Classic" }) to filter by both fields.

Practice

1. Why is it important to use good query patterns in MongoDB?

easy

A. They help find data faster and use less resources.

B. They make the database larger in size.

C. They slow down the application.

D. They remove data automatically.

Solution

1. Step 1: Understand query patterns

   Good query patterns are designed to find data quickly and efficiently.

2. Step 2: Recognize benefits

   Using good patterns reduces resource use and speeds up the app.

3. Final Answer:

   They help find data faster and use less resources. -> Option A

4. Quick Check:

   Good query patterns = faster data access [OK]

Hint: Good queries = faster results and less resource use [OK]

Common Mistakes:

• Thinking query patterns increase database size
• Believing query patterns slow down the app
• Assuming query patterns delete data

2. Which of the following is the correct way to write a simple MongoDB query to find documents where age is 25?

easy

A. db.collection.find({age: "25"})

B. db.collection.find(age == 25)

C. db.collection.find({age: 25})

D. db.collection.find({age: $eq: 25})

Solution

1. Step 1: Check MongoDB query syntax

   The correct syntax uses a JSON object with field and value inside find().

2. Step 2: Identify correct option

   db.collection.find({age: 25}) uses {age: 25} which is valid syntax for equality.

3. Final Answer:

   db.collection.find({age: 25}) -> Option C

4. Quick Check:

   Correct MongoDB query syntax = db.collection.find({age: 25}) [OK]

Hint: Use JSON object with field: value inside find() [OK]

Common Mistakes:

• Using == inside find() instead of JSON object
• Putting value as string when it should be number
• Incorrect use of $eq without braces

3. Given the collection users with documents:
{name: "Alice", age: 30}, {name: "Bob", age: 25}, {name: "Carol", age: 30}
What will db.users.find({age: 30}) return?

medium

A. [{name: "Bob", age: 25}]

B. [{name: "Alice", age: 30}, {name: "Carol", age: 30}]

C. []

D. SyntaxError

Solution

1. Step 1: Understand the query condition

   The query looks for documents where age equals 30.

2. Step 2: Match documents in collection

   Alice and Carol have age 30, so both match and are returned.

3. Final Answer:

   [{name: "Alice", age: 30}, {name: "Carol", age: 30}] -> Option B

4. Quick Check:

   Find age 30 returns Alice and Carol [OK]

Hint: Match field value exactly to get correct documents [OK]

Common Mistakes:

• Returning documents with age 25
• Expecting empty result
• Thinking query causes syntax error

4. What is wrong with this MongoDB query to find users older than 20?
db.users.find({age: > 20})

medium

A. The field name 'age' is misspelled.

B. The find() method cannot use comparison operators.

C. The query is missing a closing parenthesis.

D. The comparison operator > is used incorrectly inside the query object.

Solution

1. Step 1: Analyze query syntax

   The query uses > directly inside the object, which is invalid in MongoDB.

2. Step 2: Correct usage of comparison operators

   MongoDB requires operators like $gt inside an object: {age: {$gt: 20}}.

3. Final Answer:

   The comparison operator > is used incorrectly inside the query object. -> Option D

4. Quick Check:

   Use $gt for greater than in queries [OK]

Hint: Use $gt, $lt for comparisons inside query objects [OK]

Common Mistakes:

• Using > directly instead of $gt
• Assuming find() can't use comparisons
• Ignoring correct syntax for operators

5. You want to speed up queries that search users by their email. Which query pattern helps most in MongoDB?

hard

A. Use a simple equality query on the email field and create an index on email.

B. Use a regex query on email without any index.

C. Scan all documents and filter emails in application code.

D. Store emails in a separate collection without indexes.

Solution

1. Step 1: Identify efficient query pattern

   Simple equality queries on indexed fields are fastest in MongoDB.

2. Step 2: Understand index role

   Creating an index on email lets MongoDB find matches quickly without scanning all documents.

3. Final Answer:

   Use a simple equality query on the email field and create an index on email. -> Option A

4. Quick Check:

   Index + simple query = fast search [OK]

Hint: Index fields you query often for speed [OK]

Common Mistakes:

• Using regex without index causes slow queries
• Filtering in app wastes resources
• Not indexing searchable fields