Pipeline mental model (stages flow) in MongoDB - Time & Space Complexity

Time Complexity: Pipeline mental model (stages flow)

O(n log n)

Understanding Time Complexity

When using a MongoDB pipeline, we want to know how the time it takes grows as we add more data or stages.

We ask: How does the pipeline's work increase when the input or steps grow?

Scenario Under Consideration

Analyze the time complexity of the following MongoDB aggregation pipeline.

db.orders.aggregate([
  { $match: { status: "shipped" } },
  { $group: { _id: "$customerId", total: { $sum: "$amount" } } },
  { $sort: { total: -1 } },
  { $limit: 5 }
])

This pipeline filters shipped orders, groups by customer to sum amounts, sorts totals descending, and limits to top 5.

Identify Repeating Operations

Look for repeated work inside the pipeline.

• Primary operation: Scanning all documents to filter and group.
• How many times: Each document is processed once through each stage in order.

How Execution Grows With Input

As the number of orders grows, the pipeline must check and group more documents.

Input Size (n)	Approx. Operations
10	About 10 document checks and groupings
100	About 100 document checks and groupings
1000	About 1000 document checks and groupings

Pattern observation: The work grows roughly in direct proportion to the number of documents.

Final Time Complexity

Time Complexity: O(n log n)

This means the pipeline's work grows roughly linearly with the number of input documents, but sorting adds a logarithmic factor.

Common Mistake

[X] Wrong: "Adding more stages always multiplies the time by the number of stages."

[OK] Correct: Each document passes through stages one after another, so time grows mostly with input size, not simply by multiplying stages.

Interview Connect

Understanding how pipeline stages process data step-by-step helps you explain performance clearly and shows you know how MongoDB handles data flow.

Self-Check

"What if we added a $lookup stage that joins with another collection? How would the time complexity change?"

Practice

1. What does each stage in a MongoDB aggregation pipeline do?

easy

A. Runs a SQL query on the data

B. Creates a new database

C. Transforms or filters data before passing it to the next stage

D. Deletes the entire collection

Solution

1. Step 1: Understand the pipeline concept

   Each stage in a pipeline processes data step-by-step, modifying or filtering it.

2. Step 2: Identify the role of stages

   Stages do not create databases or delete collections; they only transform or filter data.

3. Final Answer:

   Transforms or filters data before passing it to the next stage -> Option C

4. Quick Check:

   Pipeline stages transform or filter data [OK]

Hint: Remember: pipeline stages change data step-by-step [OK]

Common Mistakes:

• Thinking stages create or delete collections
• Confusing pipeline with database commands
• Assuming stages run SQL queries

2. Which of the following is the correct syntax to start an aggregation pipeline in MongoDB?

easy

A. db.collection.find({ $match: { status: 'A' } })

B. db.collection.update({ $match: { status: 'A' } })

C. db.collection.insert([{ $match: { status: 'A' } }])

D. db.collection.aggregate([ { $match: { status: 'A' } } ])

Solution

1. Step 1: Identify aggregation pipeline syntax

   The aggregation pipeline uses the aggregate() method with an array of stages.

2. Step 2: Compare options

   Only db.collection.aggregate([ { $match: { status: 'A' } } ]) uses aggregate() with a pipeline stage ($match). Others use find, insert, or update incorrectly.

3. Final Answer:

   db.collection.aggregate([ { $match: { status: 'A' } } ]) -> Option D

4. Quick Check:

   aggregate() starts pipelines [OK]

Hint: aggregate() method always starts a pipeline [OK]

Common Mistakes:

• Using find() instead of aggregate() for pipelines
• Trying to insert pipeline stages
• Using update() with pipeline syntax

3. Given the pipeline: [{ $match: { age: { $gte: 18 } } }, { $group: { _id: '$city', count: { $sum: 1 } } }], what does the output represent?

medium

A. Count of people grouped by city who are 18 or older

B. List of all people younger than 18

C. Sum of ages for each city

D. All documents without filtering

Solution

1. Step 1: Analyze the $match stage

   This stage filters documents where age is 18 or more.

2. Step 2: Analyze the $group stage

   Groups filtered documents by city and counts how many per city.

3. Final Answer:

   Count of people grouped by city who are 18 or older -> Option A

4. Quick Check:

   $match filters, $group counts by city [OK]

Hint: $match filters, $group aggregates data [OK]

Common Mistakes:

• Confusing $sum with sum of ages
• Ignoring the filter condition
• Assuming output lists all people

4. What is wrong with this pipeline? [{ $match: { score: { $gt: 50 } } }, { $project: { score: 1, name: 1 } }, { $match: { name: 'Alice' } }]

medium

A. Using two $match stages is not allowed

B. The pipeline syntax is correct and will work as expected

C. The $project stage must include _id field explicitly

D. The second $match stage should come before $project

Solution

1. Step 1: Check multiple $match stages

   MongoDB allows multiple $match stages anywhere in the pipeline.

2. Step 2: Check $project usage

   $project can select fields; _id is included by default unless excluded explicitly.

3. Final Answer:

   The pipeline syntax is correct and will work as expected -> Option B

4. Quick Check:

   Multiple $match and $project usage is valid [OK]

Hint: Multiple $match stages are allowed anywhere [OK]

Common Mistakes:

• Thinking multiple $match stages are invalid
• Assuming _id must be included explicitly
• Believing $project must come last

5. You want to find the average price of products in each category but only for products with stock greater than 0. Which pipeline correctly achieves this?

hard

A. [{ $match: { stock: { $gt: 0 } } }, { $group: { _id: '$category', avgPrice: { $avg: '$price' } } }]

B. [{ $group: { _id: '$category', avgPrice: { $avg: '$price' } } }, { $match: { stock: { $gt: 0 } } }]

C. [{ $project: { category: 1, price: 1, stock: 1 } }, { $group: { _id: '$category', avgPrice: { $avg: '$price' } } }]

D. [{ $match: { price: { $gt: 0 } } }, { $group: { _id: '$category', avgPrice: { $avg: '$stock' } } }]

Solution

1. Step 1: Filter products with stock > 0 first

   The $match stage must come first to filter only products in stock.

2. Step 2: Group by category and calculate average price

   Use $group with _id as category and $avg on price to get average price per category.

3. Final Answer:

   [{ $match: { stock: { $gt: 0 } } }, { $group: { _id: '$category', avgPrice: { $avg: '$price' } } }] -> Option A

4. Quick Check:

   Filter then group for correct average [OK]

Hint: Filter first, then group to aggregate correctly [OK]

Common Mistakes:

• Grouping before filtering causes wrong results
• Averaging wrong fields
• Filtering on price instead of stock