Query optimization in Firebase - Time & Space Complexity

Time Complexity: Query optimization

O(1)

Understanding Time Complexity

When using Firebase to get data, how fast the query runs matters a lot. We want to know how the time it takes changes when we ask for more data or add filters.

We ask: How does the number of operations grow as we change the query?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

const db = firebase.firestore();
const query = db.collection('users')
  .where('age', '>=', 18)
  .orderBy('age')
  .limit(50);
const snapshot = await query.get();

This code fetches up to 50 users who are 18 or older, sorted by age.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: The query.get() call that fetches documents from the database.
• How many times: This call happens once per query, but internally it may scan multiple documents to find matches.

How Execution Grows With Input

As the number of matching documents grows, the query scans more data to find the right results.

Input Size (n)	Approx. Api Calls/Operations
10	Scans about 10 documents to find matches
100	Scans about 50 documents to find matches
1000	Scans about 50 documents to find matches

Pattern observation: The number of documents scanned grows roughly linearly with the number of matching documents up to the limit (50), then remains constant.

Final Time Complexity

Time Complexity: O(1)

This means the time to run the query is constant, bounded by the fixed limit of 50 documents checked.

Common Mistake

[X] Wrong: "Adding a limit means Firebase scans all matching documents before applying the limit."

[OK] Correct: Firebase applies the limit during query execution, stopping after reading up to 50 matching documents.

Interview Connect

Understanding how queries scale helps you design better apps and answer questions about performance clearly and confidently.

Self-Check

"What if we added an index on the 'age' field? How would the time complexity change?"

Practice

1. What is the main benefit of using query optimization in Firebase?

easy

A. It makes your app faster and reduces costs by fetching only needed data.

B. It automatically backs up your database.

C. It increases the size of your database.

D. It disables security rules temporarily.

Solution

1. Step 1: Understand query optimization purpose

   Query optimization aims to improve performance and reduce costs by limiting data fetched.

2. Step 2: Identify correct benefit

   Only "It makes your app faster and reduces costs by fetching only needed data." describes faster app and cost reduction by fetching needed data.

3. Final Answer:

   It makes your app faster and reduces costs by fetching only needed data. -> Option A

4. Quick Check:

   Query optimization = faster app and lower cost [OK]

Hint: Optimization means fetching only what you need [OK]

Common Mistakes:

• Thinking optimization backs up data
• Assuming optimization increases database size
• Confusing optimization with security settings

2. Which Firebase query syntax correctly limits results to 10 documents ordered by 'score'?

easy

A. db.collection('games').orderBy('score').limit(10)

B. db.collection('games').limit(10).orderBy('score')

C. db.collection('games').where('score', '==', 10).orderBy('score')

D. db.collection('games').orderBy('score', 10)

Solution

1. Step 1: Check correct method order

   In Firebase, orderBy must come before limit to sort then limit results.

2. Step 2: Validate syntax correctness

   db.collection('games').orderBy('score').limit(10) uses correct chaining: orderBy('score').limit(10). Others misuse order or parameters.

3. Final Answer:

   db.collection('games').orderBy('score').limit(10) -> Option A

4. Quick Check:

   orderBy then limit = correct syntax [OK]

Hint: Always orderBy before limit in Firebase queries [OK]

Common Mistakes:

• Placing limit before orderBy
• Using where instead of limit for count
• Passing number as second orderBy argument

3. Given this query:

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

What will this query return?

medium

A. All users younger than 18.

B. An error because orderBy and where fields differ.

C. The first 3 users aged 18 or older, ordered by age ascending.

D. The last 3 users regardless of age.

Solution

1. Step 1: Analyze where and orderBy fields

   Both where and orderBy use 'age', which is allowed and required for range filters.

2. Step 2: Understand limit effect

   Limit(3) returns only first 3 documents matching criteria ordered by age ascending.

3. Final Answer:

   The first 3 users aged 18 or older, ordered by age ascending. -> Option C

4. Quick Check:

   where and orderBy on same field + limit = first 3 matching [OK]

Hint: where range and orderBy must use same field [OK]

Common Mistakes:

• Thinking it returns users younger than 18
• Assuming error due to different fields
• Ignoring limit effect

4. You wrote this query:

db.collection('orders').where('status', '==', 'shipped').orderBy('date')

But it throws an error about missing index. What should you do?

medium

A. Remove orderBy to fix the error.

B. Create a composite index on 'status' and 'date' fields in Firebase console.

C. Change '==' to '>=' in where clause.

D. Use limit(1) to avoid indexing.

Solution

1. Step 1: Understand composite index requirement

   Queries with where and orderBy on different fields need a composite index in Firebase.

2. Step 2: Fix error by creating index

   Creating a composite index on 'status' and 'date' fields resolves the error.

3. Final Answer:

   Create a composite index on 'status' and 'date' fields in Firebase console. -> Option B

4. Quick Check:

   Missing index error = create composite index [OK]

Hint: Missing index error means create composite index [OK]

Common Mistakes:

• Removing orderBy instead of indexing
• Changing operators incorrectly
• Using limit to bypass index requirement

5. You want to optimize a query to fetch only active users with scores above 50, ordered by score descending, limited to 5 results. Which query is best?

hard

A. db.collection('users').where('active', '==', true).orderBy('score').limit(5)

B. db.collection('users').orderBy('score', 'desc').limit(5).where('active', '==', true).where('score', '>', 50)

C. db.collection('users').where('score', '>', 50).limit(5).orderBy('score', 'desc').where('active', '==', true)

D. db.collection('users').where('active', '==', true).where('score', '>', 50).orderBy('score', 'desc').limit(5)

Solution

1. Step 1: Check correct chaining and order

   db.collection('users').where('active', '==', true).where('score', '>', 50).orderBy('score', 'desc').limit(5) correctly chains where filters first, then orderBy with descending, then limit.

2. Step 2: Validate query logic

   It filters active users with score > 50, orders by score descending, and limits to 5 results as required.

3. Final Answer:

   db.collection('users').where('active', '==', true).where('score', '>', 50).orderBy('score', 'desc').limit(5) -> Option D

4. Quick Check:

   Filter then orderBy desc then limit = optimized query [OK]

Hint: Chain where filters before orderBy and limit [OK]

Common Mistakes:

• Placing limit before where
• Incorrect orderBy direction
• Missing one of the filters