Aggregation for reporting dashboards in MongoDB - Time & Space Complexity

Time Complexity: Aggregation for reporting dashboards

O(n)

Understanding Time Complexity

When building reporting dashboards, we often use aggregation to summarize data quickly.

We want to know how the time to get these summaries grows as the data grows.

Scenario Under Consideration

Analyze the time complexity of the following aggregation pipeline.

db.sales.aggregate([
  { $match: { status: "completed" } },
  { $group: { _id: "$region", totalSales: { $sum: "$amount" } } },
  { $sort: { totalSales: -1 } }
])

This pipeline filters completed sales, groups them by region summing amounts, then sorts by total sales.

Identify Repeating Operations

Look for repeated work inside the pipeline.

• Primary operation: Scanning each sale document once to filter and group.
• How many times: Once per document in the sales collection.

How Execution Grows With Input

As the number of sales grows, the work grows too.

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

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

Final Time Complexity

Time Complexity: O(n)

This means the time to run the aggregation grows linearly with the number of sales records.

Common Mistake

[X] Wrong: "Grouping by region makes the query slower by the square of the data size."

[OK] Correct: Grouping just collects data as it scans once; it does not multiply work by data size again.

Interview Connect

Understanding how aggregation scales helps you explain how dashboards stay fast even with lots of data.

Self-Check

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

Practice

1. What is the main purpose of using the $group stage in a MongoDB aggregation pipeline for reporting dashboards?

easy

A. To add new fields to documents without changing existing ones

B. To combine documents and calculate summary values like totals or averages

C. To sort documents in ascending or descending order

D. To filter documents based on specific conditions

Solution

1. Step 1: Understand the role of $group

   The $group stage collects documents into groups and calculates summary statistics like sums or averages.

2. Step 2: Compare with other stages

   $match filters, $sort orders, and $addFields adds fields, but only $group aggregates data.

3. Final Answer:

   To combine documents and calculate summary values like totals or averages -> Option B

4. Quick Check:

   $group = summary aggregation [OK]

Hint: Remember $group is for summarizing data by categories [OK]

Common Mistakes:

• Confusing $group with $match filtering
• Thinking $group sorts data
• Assuming $group adds fields without aggregation

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

easy

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

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

C. db.collection.group({ status: 'active' })

D. db.collection.aggregateMatch({ status: 'active' })

Solution

1. Step 1: Identify the aggregation method

   The correct method to start aggregation is aggregate() with an array of stages.

2. Step 2: Check syntax correctness

   db.collection.aggregate([{ $match: { status: 'active' } }]) is valid; others use wrong methods or syntax.

3. Final Answer:

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

4. Quick Check:

   aggregate() starts pipeline [OK]

Hint: Use aggregate() with an array of stages to start [OK]

Common Mistakes:

• Using find() instead of aggregate() for pipelines
• Trying to use group() as a method
• Incorrect method names like aggregateMatch()

3. Given the collection sales with documents like { product: 'A', quantity: 5 } and { product: 'B', quantity: 3 }, what will this aggregation return?

db.sales.aggregate([
  { $group: { _id: '$product', totalQuantity: { $sum: '$quantity' } } },
  { $sort: { totalQuantity: -1 } }
])

medium

A. [{ _id: 'A', totalQuantity: 8 }]

B. [{ _id: 'B', totalQuantity: 3 }, { _id: 'A', totalQuantity: 5 }]

C. [{ _id: 'A', totalQuantity: 5 }, { _id: 'B', totalQuantity: 3 }]

D. SyntaxError due to missing fields

Solution

1. Step 1: Group by product and sum quantity

   The $group stage groups documents by product and sums their quantities: 'A' -> 5, 'B' -> 3.

2. Step 2: Sort by totalQuantity descending

   The $sort orders results by totalQuantity descending, so 'A' (5) comes before 'B' (3).

3. Final Answer:

   [{ _id: 'A', totalQuantity: 5 }, { _id: 'B', totalQuantity: 3 }] -> Option C

4. Quick Check:

   Group sums then sort desc = correct order [OK]

Hint: Group sums then sort descending by total [OK]

Common Mistakes:

• Mixing up sort order ascending vs descending
• Expecting combined total instead of grouped sums
• Thinking syntax error occurs

4. Identify the error in this aggregation pipeline:

db.orders.aggregate([
  { $match: { status: 'completed' } },
  { $group: { _id: '$customerId', total: { $sum: '$amount' } } },
  { $sort: { total: 1 } },
  { $project: { customerId: 1, total: 1 } }
])

medium

A. The $sort stage must come before $group

B. The $sum operator cannot be used inside $group

C. The $match stage should be after $group

D. The $project stage uses a field not present in the grouped output

Solution

1. Step 1: Check fields after $group

   After grouping by _id: '$customerId', the output fields are _id and total. The original customerId field is renamed to _id.

2. Step 2: Analyze $project stage

   The $project tries to include customerId, which does not exist; it should use _id instead.

3. Final Answer:

   The $project stage uses a field not present in the grouped output -> Option D

4. Quick Check:

   Use _id after $group, not original field [OK]

Hint: After $group, use _id field names in $project [OK]

Common Mistakes:

• Assuming original fields remain after $group
• Placing $sort before $group incorrectly
• Misusing $sum outside $group

5. You want to create a dashboard showing the average order amount per customer, but only for customers with more than 3 orders. Which aggregation pipeline correctly achieves this?

hard

A. [{ $group: { _id: '$customerId', avgAmount: { $avg: '$amount' }, count: { $sum: 1 } } }, { $match: { count: { $gt: 3 } } }]

B. [{ $match: { count: { $gt: 3 } } }, { $group: { _id: '$customerId', avgAmount: { $avg: '$amount' } } }]

C. [{ $group: { _id: '$customerId', avgAmount: { $avg: '$amount' } } }, { $match: { avgAmount: { $gt: 3 } } }]

D. [{ $group: { _id: '$customerId', avgAmount: { $avg: '$amount' } } }, { $sort: { avgAmount: -1 } }]

Solution

1. Step 1: Group by customer and calculate average and count

   Use $group to get average order amount and count of orders per customer.

2. Step 2: Filter customers with more than 3 orders

   Apply $match after grouping to keep only customers where count > 3.

3. Final Answer:

   [{ $group: { _id: '$customerId', avgAmount: { $avg: '$amount' }, count: { $sum: 1 } } }, { $match: { count: { $gt: 3 } } }] -> Option A

4. Quick Check:

   Group then filter by count > 3 [OK]

Hint: Filter after grouping to use aggregated counts [OK]

Common Mistakes:

• Filtering by count before grouping
• Filtering by avgAmount instead of count
• Missing count calculation in $group