Transaction basics in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a transaction in Firebase?

A transaction in Firebase is a way to ensure that a read and write operation happen together safely. It helps keep data consistent by retrying if something changes during the process.

beginner

Why do we use transactions instead of simple writes?

We use transactions to avoid conflicts when multiple users try to change the same data at the same time. Transactions make sure the final data is correct and no updates are lost.

intermediate

What happens if data changes during a Firebase transaction?

If data changes while a transaction is running, Firebase automatically retries the transaction with the new data until it succeeds or fails after several attempts.

beginner

How do you start a transaction in Firebase?

You start a transaction by calling the transaction method on a database reference and providing a function that updates the data based on the current value.

intermediate

What is the role of the update function inside a Firebase transaction?

The update function receives the current data and returns the new data to save. It decides how to change the data safely during the transaction.

What does a Firebase transaction guarantee?

A Automatic data backup

B Faster data retrieval

C Unlimited data storage

D Data consistency during concurrent updates

Transactions ensure data consistency when multiple users update the same data at the same time.

What triggers Firebase to retry a transaction?

A If the data changes during the transaction

B If the network is slow

C If the user logs out

D If the database is empty

Firebase retries transactions automatically if the data changes while the transaction is running.

Which method do you use to run a transaction in Firebase Realtime Database?

A transaction()

B set()

C update()

D push()

The transaction() method runs a transaction on a database reference.

What does the update function inside a transaction receive?

A User credentials

B Current data snapshot

C Database rules

D Network status

The update function receives the current data to decide how to update it safely.

When should you use a transaction in Firebase?

A When backing up data

B When reading data only once

C When multiple users might update the same data simultaneously

D When deleting data

Transactions are used to handle simultaneous updates safely.

Explain how Firebase transactions help maintain data consistency.

Think about what happens if two users update the same data at once.

Describe the steps to perform a transaction in Firebase Realtime Database.

Focus on the method and the function you pass to it.

Practice

1. What is the main purpose of using a transaction in Firebase?

easy

A. To speed up data retrieval

B. To ensure data changes are safe and consistent

C. To store large files

D. To send notifications to users

Solution

1. Step 1: Understand transaction purpose

   Transactions are designed to keep data changes safe and consistent when multiple users might update the same data.

2. Step 2: Eliminate unrelated options

   Speeding up retrieval, storing files, or sending notifications are not the main goals of transactions.

3. Final Answer:

   To ensure data changes are safe and consistent -> Option B

4. Quick Check:

   Transaction purpose = safe and consistent data [OK]

Hint: Transactions protect data integrity during concurrent updates [OK]

Common Mistakes:

• Thinking transactions speed up data retrieval
• Confusing transactions with file storage
• Assuming transactions send notifications

2. Which of the following is the correct way to start a transaction in Firebase Realtime Database?

easy

A. database.ref('path').transaction(updateFunction)

B. database.ref('path').setTransaction(updateFunction)

C. database.transaction('path', updateFunction)

D. database.ref('path').runTransaction(updateFunction)

Solution

1. Step 1: Recall Firebase transaction syntax

   The correct method to start a transaction is calling transaction() on a database reference.

2. Step 2: Check each option

   database.ref('path').transaction(updateFunction) uses ref('path').transaction(updateFunction), which is correct. Options A, B, and D use incorrect method names or call patterns.

3. Final Answer:

   database.ref('path').transaction(updateFunction) -> Option A

4. Quick Check:

   Correct method is .transaction() on ref [OK]

Hint: Use .transaction() on a database reference to start [OK]

Common Mistakes:

• Using .setTransaction() which does not exist
• Calling transaction directly on database object
• Using .runTransaction() which is invalid

3. Consider this transaction code snippet:

database.ref('counter').transaction(currentValue => {
  if (currentValue === null) {
    return 1;
  } else {
    return currentValue + 1;
  }
});

What will be the value of 'counter' after this transaction if it was initially 5?

medium

A. 6

B. 1

C. null

D. 5

Solution

1. Step 1: Analyze the transaction function logic

   The function checks if the current value is null; if so, it returns 1. Otherwise, it returns currentValue + 1.

2. Step 2: Apply initial value 5

   Since currentValue is 5 (not null), the function returns 5 + 1 = 6.

3. Final Answer:

   6 -> Option A

4. Quick Check:

   5 + 1 = 6 [OK]

Hint: If value exists, transaction adds 1; else sets to 1 [OK]

Common Mistakes:

• Assuming value stays the same
• Confusing null check logic
• Returning 1 regardless of current value

4. What is wrong with this Firebase transaction code?

database.ref('score').transaction(() => {
  database.ref('score').set(10);
  return 20;
});

medium

A. You cannot return a value in a transaction function

B. Calling set() inside transaction causes an error

C. Reads must happen before writes inside the transaction function

D. Transaction function must be async

Solution

1. Step 1: Understand transaction function rules

   All reads must happen before any writes inside the transaction function to ensure consistency.

2. Step 2: Identify the problem in code

   The code calls set(10) inside the transaction function before returning a new value, which violates the rule.

3. Final Answer:

   Reads must happen before writes inside the transaction function -> Option C

4. Quick Check:

   Transaction rule: read before write [OK]

Hint: Do all reads before any writes inside transaction function [OK]

Common Mistakes:

• Calling set() inside transaction function
• Returning a value is allowed and required
• Thinking transaction function must be async

5. You want to increment a user's points only if their current points are less than 100. Which transaction function correctly implements this logic?

database.ref('users/user1/points').transaction(currentPoints => {
  // Your code here
});

hard

A. if (currentPoints === null) { return 0; } else { return 100; }

B. if (currentPoints >= 100) { return currentPoints + 1; } else { return currentPoints; }

C. return currentPoints + 1;

D. if (currentPoints === null || currentPoints < 100) { return (currentPoints || 0) + 1; } else { return currentPoints; }

Solution

1. Step 1: Understand the condition to increment points

   Points should increment only if currentPoints is less than 100 or if it is null (no points yet).

2. Step 2: Check each option logic

   if (currentPoints === null || currentPoints < 100) { return (currentPoints || 0) + 1; } else { return currentPoints; } increments points by 1 if currentPoints is null or less than 100, else returns currentPoints unchanged. This matches the requirement. if (currentPoints >= 100) { return currentPoints + 1; } else { return currentPoints; } increments when points are 100 or more, which is wrong. return currentPoints + 1; always increments ignoring the limit. if (currentPoints === null) { return 0; } else { return 100; } resets points incorrectly.

3. Final Answer:

   if (currentPoints === null || currentPoints < 100) { return (currentPoints || 0) + 1; } else { return currentPoints; } -> Option D

4. Quick Check:

   Increment only if points < 100 or null [OK]

Hint: Check null or less than 100 before incrementing [OK]

Common Mistakes:

• Incrementing points when already 100 or more
• Ignoring null initial value
• Resetting points instead of incrementing