Transaction basics in Firebase - Mini Project: Build & Apply

Transaction basics

📖 Scenario: You are building a simple inventory system using Firebase Realtime Database. You want to safely update the stock count of a product when a purchase happens, ensuring no conflicts if multiple users buy at the same time.

🎯 Goal: Build a Firebase transaction that reads the current stock of a product, decreases it by the purchased amount only if enough stock exists, and writes the updated stock back safely.

📋 What You'll Learn

Create a reference to the product stock in Firebase Realtime Database

Set a purchase amount variable

Use a Firebase transaction to update the stock safely

Complete the transaction with proper success handling

💡 Why This Matters

🌍 Real World

Inventory systems need to update stock counts safely when multiple users buy items at the same time. Firebase transactions help prevent conflicts and data corruption.

💼 Career

Understanding Firebase transactions is important for developers building real-time apps that require safe concurrent updates to shared data.

1

Create a Firebase reference to product stock

Create a variable called productStockRef that references the path 'products/product123/stock' in the Firebase Realtime Database using firebase.database().ref().

Firebase

# Your code here

Hint

Use firebase.database().ref('path') to create a reference to a location in the database.

2

Set the purchase amount variable

Create a variable called purchaseAmount and set it to 3 to represent the number of items being bought.

Firebase

const productStockRef = firebase.database().ref('products/product123/stock');
# Your code here

Hint

Just create a constant variable with the number 3.

3

Use a Firebase transaction to update stock safely

Call productStockRef.transaction with a function that takes the current stock value as currentStock. Inside the function, if currentStock is null, return null. If currentStock is less than purchaseAmount, return undefined to abort. Otherwise, return currentStock - purchaseAmount.

Firebase

const productStockRef = firebase.database().ref('products/product123/stock');
const purchaseAmount = 3;
# Your code here

Hint

The transaction function receives the current value. Return the new value or undefined to abort.

4

Complete the transaction with success handling

Add a second argument to productStockRef.transaction which is a callback function with parameters error, committed, and snapshot. Inside the callback, if error exists, handle it (for example, log it). If committed is true, the transaction succeeded. Use snapshot.val() to get the updated stock.

Firebase

const productStockRef = firebase.database().ref('products/product123/stock');
const purchaseAmount = 3;

productStockRef.transaction(currentStock => {
  if (currentStock === null) {
    return null;
  }
  if (currentStock  {
  # Your code here
});

Hint

The second argument to transaction is a callback for completion status.

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