How MongoDB scans documents - Visual Walkthrough

Concept Flow - How MongoDB scans documents

Start Query

↓

Check for Index

↓

Use Index

↓

Fetch Docs

↓

Apply Filters

↓

Return Results

MongoDB first checks if an index can be used. If yes, it uses the index to find documents quickly. If no index is available, it scans all documents in the collection. Then it applies filters and returns the matching documents.

Execution Sample

MongoDB

db.users.find({age: {$gt: 30}})

This query finds all user documents where the age is greater than 30.

Execution Table

Step	Action	Index Used?	Documents Scanned	Documents Matched	Result
1	Start query execution	N/A	0	0	Query begins
2	Check for index on 'age'	Yes	0	0	Index found
3	Use index to find candidate doc IDs	Yes	0	0	Candidate doc IDs found
4	Fetch documents by IDs	Yes	5	0	Documents retrieved
5	Apply filter age > 30	Yes	5	3	3 documents match
6	Return matching documents	Yes	5	3	3 documents returned
7	End query execution	Yes	5	3	Query complete

💡 Query ends after returning all documents matching age > 30 using index scan

Variable Tracker

Variable	Start	After Step 3	After Step 5	Final
Documents Scanned	0	0	5	5
Documents Matched	0	0	3	3
Index Used	N/A	Yes	Yes	Yes

Key Moments - 2 Insights

Why does MongoDB scan fewer documents when an index is used?

Because the index helps MongoDB quickly find only the documents that might match, so it doesn't have to look at every document in the collection (see execution_table steps 2 and 3).

What happens if there is no index on the queried field?

MongoDB will scan every document in the collection to check if it matches the query, which is slower (see concept_flow where 'No' leads to 'Full Collection Scan').

Visual Quiz - 3 Questions

Look at the execution_table, at which step does MongoDB apply the filter condition?

A Step 3

B Step 2

C Step 5

D Step 6

💡 Hint

Check the 'Action' column in execution_table where filter is applied

According to variable_tracker, how many documents were matched after applying the filter?

A 3

B 0

C 5

D None

💡 Hint

Look at 'Documents Matched' after Step 5 in variable_tracker

If there was no index on 'age', what would change in the execution flow?

A MongoDB would use the index anyway

B MongoDB would scan all documents in the collection

C MongoDB would return no results

D MongoDB would skip applying filters

💡 Hint

Refer to concept_flow where 'No' index leads to 'Full Collection Scan'

Concept Snapshot

MongoDB scans documents by first checking for an index on the queried field.
If an index exists, it uses it to quickly find matching documents.
Without an index, MongoDB scans every document in the collection.
Filters are applied after fetching documents.
Using indexes improves query speed by reducing scanned documents.

Full Transcript

When MongoDB runs a query, it first checks if there is an index on the field used in the query. If an index exists, MongoDB uses it to find matching document IDs quickly without scanning the entire collection. Then it fetches those documents and applies the filter condition to return only the matching documents. If no index exists, MongoDB scans every document in the collection to find matches, which is slower. This process helps MongoDB efficiently return query results.