Updating specific fields in Firebase - Time & Space Complexity

Time Complexity: Updating specific fields

O(1)

Understanding Time Complexity

When updating specific fields in a Firebase document, it's important to know how the time to complete the update changes as the number of fields or documents grows.

We want to understand how the update operation scales with input size.

Scenario Under Consideration

Analyze the time complexity of updating specific fields in a document.

const docRef = firestore.collection('users').doc('user123');
await docRef.update({
  age: 30,
  city: 'New York'
});
    

This code updates only the age and city fields of a single user document.

Identify Repeating Operations

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

• Primary operation: One update API call to modify specific fields in a document.
• How many times: Exactly once per update request, regardless of how many fields are updated.

How Execution Grows With Input

Updating more fields in the same document still uses a single API call, so the number of calls stays the same.

Input Size (number of fields)	Approx. API Calls/Operations
2	1
10	1
100	1

Pattern observation: The number of API calls does not increase with the number of fields updated in a single document.

Final Time Complexity

Time Complexity: O(1)

This means updating specific fields in one document takes the same amount of time no matter how many fields you change.

Common Mistake

[X] Wrong: "Updating more fields means more API calls and longer time."

[OK] Correct: Because Firebase sends one update request per document, updating multiple fields in that document is done in a single call.

Interview Connect

Understanding how updates scale helps you design efficient data operations and shows you know how cloud services handle requests behind the scenes.

Self-Check

"What if we updated multiple documents instead of one? How would the time complexity change?"