Crunch Data Where It Lives (the Aggregation Pipeline)

Why this matters

The aggregation pipeline is MongoDB's answer to SQL GROUP BY, WHERE, and SELECT — but composable as a sequence of stages. Each stage transforms the stream of documents: $match filters, $group buckets and computes accumulators, $project reshapes. Running aggregations server-side instead of pulling documents into application code is often a 100× throughput improvement on analytical queries, because you move computation to where the data lives rather than shuffling gigabytes across the network.

Demo

Count orders by status and compute total revenue per status using $match, $group, and $project.

Try it yourself

1. Add a $match stage before $group to filter only orders from the last 30 days using a createdAt date field. Verify the revenue totals change by inserting a few old-dated orders.
2. Add an $addFields stage after $group that computes avgOrderValue as totalRevenue / count. Confirm the arithmetic is correct against manually computed values.
3. Run the pipeline with and without the leading $match stage on a collection of 10,000 documents. Use explain('executionStats') to compare nReturned and totalDocsExamined at the $group stage.

References

• Aggregation Pipeline — MongoDB docs
• Aggregation Pipeline Optimization