Explain plan analysis (queryPlanner, executionStats) in MongoDB - Mini Project: Build & Apply

Analyze MongoDB Query Performance with Explain Plan

📖 Scenario: You are managing a small online bookstore database in MongoDB. You want to understand how MongoDB runs your search queries to make them faster.

🎯 Goal: Learn how to use MongoDB's explain() method to see the queryPlanner and executionStats for a query. This helps you understand how MongoDB finds data and how efficient the query is.

📋 What You'll Learn

Create a collection called books with sample book documents

Write a query to find books by a specific author

Use explain('executionStats') on the query to get detailed info

Access and understand the queryPlanner and executionStats parts of the explain output

💡 Why This Matters

🌍 Real World

Understanding explain plans helps database administrators and developers optimize queries for faster data retrieval in real applications like online stores or content management systems.

💼 Career

Knowing how to analyze query plans is a key skill for roles like database administrator, backend developer, and data engineer to improve application performance.

1

Create the books collection with sample data

Create a MongoDB collection called books and insert these exact documents: { title: 'The Hobbit', author: 'J.R.R. Tolkien', year: 1937 }, { title: '1984', author: 'George Orwell', year: 1949 }, and { title: 'Animal Farm', author: 'George Orwell', year: 1945 }.

MongoDB

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

Need a hint?

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

2

Write a query to find books by George Orwell

Write a MongoDB query called query that finds all books where the author is exactly 'George Orwell'.

MongoDB

// Create a query to find books by 'George Orwell'
// Your code here

Need a hint?

Define a variable query with the filter { author: 'George Orwell' }.

3

Use explain('executionStats') to analyze the query

Use db.books.find(query).explain('executionStats') and save the result in a variable called explainResult.

MongoDB

// Run explain with 'executionStats' on the query and save to explainResult
// Your code here

Need a hint?

Use explain('executionStats') on the find query and assign it to explainResult.

4

Access queryPlanner and executionStats from the explain result

Create two variables: planner to hold explainResult.queryPlanner and stats to hold explainResult.executionStats.

MongoDB

// Save queryPlanner and executionStats to planner and stats variables
// Your code here

Need a hint?

Assign explainResult.queryPlanner to planner and explainResult.executionStats to stats.