Why Firestore is Firebase's primary database - Performance Analysis

Time Complexity: Why Firestore is Firebase's primary database

O(n)

Understanding Time Complexity

We want to understand how Firestore handles data operations as the amount of data grows.

Specifically, how the time to read or write data changes when using Firestore.

Scenario Under Consideration

Analyze the time complexity of reading multiple documents from Firestore.

const db = firebase.firestore();
const collectionRef = db.collection('users');

async function getUsers(userIds) {
  const users = [];
  for (const id of userIds) {
    const doc = await collectionRef.doc(id).get();
    users.push(doc.data());
  }
  return users;
}
    

This code fetches user documents one by one from Firestore using their IDs.

Identify Repeating Operations

Look at what repeats as input grows.

• Primary operation: Fetching a single document with doc(id).get().
• How many times: Once for each user ID in the input list.

How Execution Grows With Input

Each user ID causes one document fetch, so the total fetches grow directly with the number of IDs.

Input Size (n)	Approx. API Calls/Operations
10	10 document fetches
100	100 document fetches
1000	1000 document fetches

Pattern observation: The number of fetches grows linearly as the input size grows.

Final Time Complexity

Time Complexity: O(n)

This means the time to fetch all documents grows directly in proportion to how many documents you want.

Common Mistake

[X] Wrong: "Fetching multiple documents at once is always faster than fetching them one by one."

[OK] Correct: While batch fetching can reduce network overhead, if you fetch documents one by one as in this code, the time grows linearly because each fetch is separate.

Interview Connect

Understanding how Firestore scales with data size helps you design apps that stay fast as they grow.

This skill shows you can think about real-world app performance, a key part of cloud development.

Self-Check

"What if we changed the code to fetch all documents in a single batch call? How would the time complexity change?"

Practice

1. Why is Firestore considered Firebase's primary database?

easy

A. Because it only stores data temporarily

B. Because it requires manual scaling for large apps

C. Because it updates data in real time and works offline

D. Because it does not support security rules

Solution

1. Step 1: Understand Firestore's real-time update feature

   Firestore automatically updates data in real time, so apps stay current without manual refresh.

2. Step 2: Recognize offline support and automatic scaling

   Firestore works offline and scales automatically, making it easy to use and reliable.

3. Final Answer:

   Because it updates data in real time and works offline -> Option C

4. Quick Check:

   Real-time + offline = Firestore primary [OK]

Hint: Remember Firestore updates live and works offline [OK]

Common Mistakes:

• Thinking Firestore needs manual scaling
• Believing Firestore lacks security rules
• Confusing Firestore with temporary storage

2. Which of the following is the correct way to define a Firestore collection reference in Firebase SDK?

easy

A. const ref = firestore.collection('users');

B. const ref = firestore.getCollection('users');

C. const ref = firestore.users.collection();

D. const ref = firestore.collection.users();

Solution

1. Step 1: Recall Firestore collection syntax

   The correct method to get a collection reference is firestore.collection('collectionName').

2. Step 2: Check each option's syntax

   Only const ref = firestore.collection('users'); uses the correct method name and syntax.

3. Final Answer:

   const ref = firestore.collection('users'); -> Option A

4. Quick Check:

   Use .collection('name') to get collection [OK]

Hint: Use .collection('name') to get Firestore collections [OK]

Common Mistakes:

• Using getCollection instead of collection
• Accessing collection as a property
• Calling collection as a method on collection

3. Given this Firestore query code, what will be the output if the 'users' collection has documents with fields {name: 'Alice', age: 30} and {name: 'Bob', age: 25}?

const snapshot = await firestore.collection('users').where('age', '>', 26).get();
const names = snapshot.docs.map(doc => doc.data().name);
console.log(names);

medium

A. ['Alice']

B. ['Bob']

C. ['Alice', 'Bob']

D. []

Solution

1. Step 1: Analyze the query condition

   The query filters users where age is greater than 26.

2. Step 2: Check which users match the condition

   Alice is 30 (matches), Bob is 25 (does not match).

3. Final Answer:

   ['Alice'] -> Option A

4. Quick Check:

   Age > 26 returns Alice only [OK]

Hint: Filter by age > 26 returns only Alice [OK]

Common Mistakes:

• Including Bob who is 25
• Returning empty array by mistake
• Returning both users ignoring filter

4. Which of the following correctly describes this Firestore security rule snippet?

service cloud.firestore {
  match /databases/{database}/documents {
    match /users/{userId} {
      allow read, write: if request.auth.uid == userId;
    }
  }
}

medium

A. It does not allow any access to users

B. It allows read and write only if user is authenticated and matches userId

C. It allows access without authentication

D. It has syntax errors in the match statements

Solution

1. Step 1: Understand the rule condition

   The rule allows read and write only if the authenticated user's ID matches the document's userId.

2. Step 2: Check for errors or incorrect logic

   The syntax is correct and the logic restricts access properly.

3. Final Answer:

   It allows read and write only if user is authenticated and matches userId -> Option B

4. Quick Check:

   Auth check with userId match = correct rule [OK]

Hint: Check if auth uid matches userId for access [OK]

Common Mistakes:

• Thinking it allows access without auth
• Assuming syntax errors exist
• Believing it denies all access

5. You want to build a chat app that works offline and syncs messages automatically when online. Why is Firestore the best choice for this?

hard

A. Because Firestore only stores data temporarily in memory

B. Because Firestore requires manual syncing and no offline support

C. Because Firestore does not support real-time updates

D. Because Firestore supports offline data persistence and real-time syncing

Solution

1. Step 1: Identify offline support in Firestore

   Firestore caches data locally, so apps work offline without errors.

2. Step 2: Recognize real-time syncing feature

   When online, Firestore syncs changes automatically to keep data updated.

3. Step 3: Compare with other options

   Options A, B, and D contradict Firestore's key features.

4. Final Answer:

   Because Firestore supports offline data persistence and real-time syncing -> Option D

5. Quick Check:

   Offline + real-time sync = Firestore best for chat [OK]

Hint: Offline persistence + real-time sync = Firestore wins [OK]

Common Mistakes:

• Thinking Firestore needs manual sync
• Believing Firestore lacks offline support
• Confusing Firestore with temporary storage