Pipeline execution order matters in MongoDB

Introduction

In MongoDB, the order of steps in a pipeline changes the final result. Each step works on the output of the previous one, so the sequence is important.

When you want to filter data before grouping it to reduce work.

When you need to sort data after filtering to get correct order.

When you want to add new fields before grouping or sorting.

When you want to limit results after sorting to get top items.

Syntax

MongoDB

[
  { stage1 },
  { stage2 },
  ...
]

Each stage is an object inside an array.

Stages run one after another in the order they appear.

Examples

First filter active users, then sort them by age ascending.

MongoDB

[
  { $match: { status: "active" } },
  { $sort: { age: 1 } }
]

First sort all users by age, then filter active ones. This is less efficient.

MongoDB

[
  { $sort: { age: 1 } },
  { $match: { status: "active" } }
]

Sample Program

This query finds users with status 'active' first, then sorts them by age from youngest to oldest.

MongoDB

db.users.aggregate([
  { $match: { status: "active" } },
  { $sort: { age: 1 } }
])

Important Notes

Changing the order of stages can change the result or make the query slower.

Always filter early to reduce data size for later stages.

Summary

Pipeline stages run in the order you write them.

Order affects both results and performance.

Filter early, then sort or group for best results.