Why should you care?

Dashboards need totals by day, top products, and funnels. find alone cannot group; aggregate can.

See it live — copy this example

Open mongosh or MongoDB Compass, select database nosqlverse, then run the example. Change one field and run again.

db.orders.insertMany([
  { status: "paid", total: 500 },
  { status: "paid", total: 700 },
  { status: "cancelled", total: 200 }
])
db.orders.aggregate([
  { $match: { status: "paid" } },
  { $group: { _id: "$status", revenue: { $sum: "$total" }, n: { $sum: 1 } } }
])

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• $match keeps paid orders.
• $group buckets by status and sums total into revenue while counting docs.
• Result: one row with revenue 1200 and n 2.

Practice next

1. Insert the sample orders.
2. Run the pipeline.
3. Add { $sort: { revenue: -1 } } at the end.
4. Group by a category field on products.
5. Add $project to rename revenue to totalSales.

Remember

aggregate runs a pipeline of stages. $match filters; $group summarizes. Order of stages matters for speed.

Daily GMV widget

Flipkart seller dashboard sums paid orders for today.

Outcome: One aggregation powers the revenue tile.