Query optimization in Firebase - Step-by-Step Execution

Process Flow - Query optimization

Start Query

↓

Analyze Query

↓

Check Indexes

↓

Use Index

↓

Fetch Data

↓

Return Results

↓

End

The query starts, checks if indexes exist for fast lookup, uses them if available, otherwise scans the whole collection, then fetches and returns results.

Execution Sample

Firebase

db.collection('users').where('age', '>=', 18).orderBy('age').limit(3)

This query fetches up to 3 users aged 18 or older, ordered by age.

Process Table

Step	Action	Index Used	Documents Scanned	Documents Returned	Performance
1	Start Query	No	0	0	N/A
2	Analyze Query for indexes	Yes	0	0	Fast
3	Use index on 'age'	Yes	5	0	Fast
4	Fetch documents matching age >= 18	Yes	5	3	Fast
5	Return 3 documents	Yes	5	3	Fast
6	End Query	Yes	5	3	Completed

💡 Query ends after returning 3 documents using index on 'age' for efficient retrieval.

Status Tracker

Variable	Start	After Step 3	After Step 4	Final
Index Used	No	Yes	Yes	Yes
Documents Scanned	0	5	5	5
Documents Returned	0	0	3	3
Performance	N/A	Fast	Fast	Fast

Key Moments - 2 Insights

Why does the query use an index instead of scanning all documents?

Because the query has a filter and order on 'age' and an index exists on that field, as shown in execution_table step 2 and 3, it uses the index for faster access.

What happens if no index exists for the query?

The query would perform a full collection scan, which is slower, as indicated by the 'No' branch in the concept_flow and would scan all documents instead of a few.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the query start fetching documents?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Action' column for when documents matching the filter are fetched.

According to variable_tracker, how many documents are scanned before returning results?

A 5

B 3

C 0

D All documents

💡 Hint

Look at 'Documents Scanned' after Step 4 in variable_tracker.

If the index on 'age' was missing, what would change in the execution_table?

A Index Used would be 'Yes' at all steps

B Documents Scanned would increase to all documents

C Documents Scanned would be fewer

D Performance would improve

💡 Hint

Refer to concept_flow where 'No' index leads to full collection scan.

Concept Snapshot

Query optimization in Firebase:
- Queries use indexes to speed up data retrieval.
- If an index exists for the filter/order fields, it is used.
- Without indexes, queries scan the whole collection (slow).
- Always create indexes for common query patterns.
- Use limit() to reduce data fetched and improve speed.

Full Transcript

This visual execution shows how Firebase query optimization works. The query starts and checks if indexes exist for the fields used in filters and ordering. If an index is found, it uses it to quickly find matching documents without scanning the entire collection. The example query filters users aged 18 or older and orders by age, using an index on 'age'. It scans 5 documents matching the criteria and returns 3 due to the limit. If no index existed, the query would scan all documents, slowing performance. This teaches the importance of indexes for efficient queries.