Firestore trigger functions in Firebase - Time & Space Complexity

Time Complexity: Firestore trigger functions

O(n)

Understanding Time Complexity

When using Firestore trigger functions, it's important to understand how the time to run your function changes as your data grows.

We want to know how the number of operations grows when many documents trigger the function.

Scenario Under Consideration

Analyze the time complexity of the following Firestore trigger function.

exports.onUserUpdate = functions.firestore
  .document('users/{userId}')
  .onUpdate((change, context) => {
    const newData = change.after.data();
    const oldData = change.before.data();
    if (newData.status !== oldData.status) {
      return updateUserStats(context.params.userId);
    }
    return null;
  });

function updateUserStats(userId) {
  // Updates stats for the user
  return admin.firestore().collection('stats').doc(userId).set({ updated: true });
}
    

This function triggers when a user document changes. It checks if the status changed, then updates stats for that user.

Identify Repeating Operations

Look for repeated actions that affect performance.

• Primary operation: The function runs once per document update event.
• How many times: It runs once for each user document that changes.

How Execution Grows With Input

As more user documents update, the function runs more times.

Input Size (n)	Approx. Operations
10	10 function runs
100	100 function runs
1000	1000 function runs

Pattern observation: The number of operations grows directly with the number of document updates.

Final Time Complexity

Time Complexity: O(n)

This means the total work grows linearly with the number of document updates triggering the function.

Common Mistake

[X] Wrong: "The function runs once and handles all document updates at once."

[OK] Correct: Each document update triggers the function separately, so the work adds up with more updates.

Interview Connect

Understanding how trigger functions scale helps you design efficient backend processes that respond well as your app grows.

Self-Check

What if the function also queried a collection of related documents for each update? How would the time complexity change?

Practice

1. What does a Firestore trigger function do in a Firebase project?

easy

A. Deletes Firestore data without any event

B. Manually updates Firestore data when called

C. Creates a new Firestore database

D. Automatically runs code when data changes in Firestore

Solution

1. Step 1: Understand Firestore triggers

   Firestore triggers are special functions that run automatically when data changes in Firestore.

2. Step 2: Identify the trigger's purpose

   They help keep your app reactive by running code on create, update, or delete events without manual calls.

3. Final Answer:

   Automatically runs code when data changes in Firestore -> Option D

4. Quick Check:

   Firestore triggers = automatic code run on data change [OK]

Hint: Triggers run code automatically on Firestore data changes [OK]

Common Mistakes:

• Thinking triggers run manually
• Confusing triggers with database creation
• Assuming triggers delete data without events

2. Which of the following is the correct syntax to create a Firestore trigger for document creation in Node.js Firebase Functions?

easy

A. exports.onCreate = functions.firestore.document('users').onCreate((snap, context) => { });

B. exports.onCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => { });

C. functions.firestore.onCreate('users/{userId}', (snap, context) => { });

D. functions.firestore.document('users/{userId}').create((snap, context) => { });

Solution

1. Step 1: Recall Firestore trigger syntax

   The correct syntax uses exports, functions.firestore.document(path).onCreate(handler).

2. Step 2: Match syntax to options

   exports.onCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => { }); matches this pattern exactly with document path and onCreate event.

3. Final Answer:

   exports.onCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => { }); -> Option B

4. Quick Check:

   Correct Firestore onCreate syntax = exports.onCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => { }); [OK]

Hint: Use exports with document(path).onCreate(handler) for create triggers [OK]

Common Mistakes:

• Missing exports keyword
• Using onCreate directly on firestore without document
• Wrong method name like create instead of onCreate

3. Given this Firestore trigger function, what will be logged when a document is updated?

exports.logUpdate = functions.firestore.document('posts/{postId}').onUpdate((change, context) => {
  const before = change.before.data();
  const after = change.after.data();
  console.log('Title before:', before.title);
  console.log('Title after:', after.title);
});

medium

A. Logs the title before and after the update

B. Logs only the new title after update

C. Logs only the old title before update

D. Throws an error because change.before is undefined

Solution

1. Step 1: Understand onUpdate trigger parameters

   The onUpdate trigger receives a change object with before and after snapshots of the document.

2. Step 2: Analyze the console logs

   The code logs before.title and after.title, so both old and new titles are printed.

3. Final Answer:

   Logs the title before and after the update -> Option A

4. Quick Check:

   onUpdate logs before and after data [OK]

Hint: onUpdate provides before and after data snapshots [OK]

Common Mistakes:

• Assuming only new data is available
• Thinking change.before is undefined
• Confusing onUpdate with onCreate

4. Identify the error in this Firestore trigger function code:

exports.deleteUser = functions.firestore.document('users/{userId}').onDelete((snap, context) => {
  const userData = snap.data;
  console.log('Deleted user:', userData.name);
});

medium

A. Missing async keyword for the function

B. onDelete trigger cannot be used on 'users/{userId}' path

C. snap.data should be snap.data() to get document data

D. context parameter is not allowed in onDelete triggers

Solution

1. Step 1: Check how to access document data

   Firestore document snapshot data is accessed by calling snap.data(), not snap.data property.

2. Step 2: Identify the error in code

   The code uses snap.data without parentheses, causing undefined userData and runtime error.

3. Final Answer:

   snap.data should be snap.data() to get document data -> Option C

4. Quick Check:

   Use snap.data() method to access document data [OK]

Hint: Use snap.data() method, not snap.data property [OK]

Common Mistakes:

• Using snap.data instead of snap.data()
• Thinking onDelete can't use context parameter
• Assuming async is always required

5. You want to create a Firestore trigger that updates a user's profile summary whenever their profile document changes. Which approach correctly ensures the trigger only runs when the 'bio' field changes, avoiding infinite loops?

hard

A. Use onUpdate trigger and compare change.before.data().bio with change.after.data().bio before updating

B. Use onWrite trigger and update the document unconditionally inside the trigger

C. Use onCreate trigger to update bio field after document creation

D. Use onUpdate trigger and update the document without checking any field changes

Solution

1. Step 1: Choose the right trigger for updates

   onUpdate triggers run on any document update, suitable for detecting changes.

2. Step 2: Prevent infinite loops by checking field changes

   Compare bio field before and after update; only proceed if bio changed to avoid recursive updates.

3. Final Answer:

   Use onUpdate trigger and compare change.before.data().bio with change.after.data().bio before updating -> Option A

4. Quick Check:

   Check field changes in onUpdate to avoid loops [OK]

Hint: Compare before and after fields in onUpdate to avoid loops [OK]

Common Mistakes:

• Using onWrite and updating unconditionally causing loops
• Using onCreate which triggers only once
• Not checking field changes before updating