Why Transaction read-then-write pattern in Firebase? - Purpose & Use Cases

The Big Idea

What if your app could magically prevent data mix-ups when many people update at once?

The Scenario

Imagine you are updating a shared shopping list on your phone while your friend is doing the same from theirs. You both try to add items at the same time without checking what the other has just added.

The Problem

Without a careful process, your updates can overwrite each other, causing lost items or wrong quantities. Manually checking and updating data is slow and can easily cause mistakes, especially when many people use the app at once.

The Solution

The transaction read-then-write pattern in Firebase helps by first reading the current data, then safely writing the update only if the data hasn't changed in the meantime. This keeps everyone's changes safe and consistent automatically.

Before vs After

✗ Before

db.collection('list').doc('shared').set({items: newItems})

✓ After

const docRef = db.collection('list').doc('shared');
db.runTransaction(transaction => {
  return transaction.get(docRef).then(doc => {
    const currentItems = doc.data().items;
    const updatedItems = updateItems(currentItems);
    transaction.update(docRef, {items: updatedItems});
  });
})

What It Enables

This pattern makes it possible to safely update shared data in real time without losing anyone's changes.

Real Life Example

In a group budgeting app, multiple users can add expenses at the same time, and the total balance updates correctly without errors or lost data.

Key Takeaways

Manual updates can overwrite each other causing data loss.

Transaction read-then-write checks data before updating to keep it safe.

This ensures consistent and reliable shared data updates.

Practice

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

easy

A. To speed up data retrieval from the database

B. To store data permanently without changes

C. To safely read and write data together without conflicts

D. To delete data automatically after a set time

Solution

1. Step 1: Understand transaction role

   Transactions allow reading and writing data atomically, meaning both happen together safely.

2. Step 2: Identify conflict prevention

   This prevents conflicts when multiple users try to update the same data at once.

3. Final Answer:

   To safely read and write data together without conflicts -> Option C

4. Quick Check:

   Transaction = safe read-write [OK]

Hint: Transactions combine read and write safely [OK]

Common Mistakes:

• Thinking transactions only speed up reads
• Assuming transactions delete data
• Believing transactions store data permanently without changes

2. Which of the following is the correct syntax to start a transaction in Firebase Firestore using JavaScript?

easy

A. db.startTransaction(() => { /* code */ })

B. db.transactionStart(() => { /* code */ })

C. db.beginTransaction(async () => { /* code */ })

D. db.runTransaction(async (transaction) => { /* code */ })

Solution

1. Step 1: Recall Firestore transaction syntax

   The correct method to run a transaction is db.runTransaction with an async callback.

2. Step 2: Check other options

   Other options like transactionStart, beginTransaction, or startTransaction are not valid Firestore methods.

3. Final Answer:

   db.runTransaction(async (transaction) => { /* code */ }) -> Option D

4. Quick Check:

   runTransaction is correct method [OK]

Hint: Use db.runTransaction with async callback [OK]

Common Mistakes:

• Using non-existent methods like transactionStart
• Forgetting async keyword in callback
• Confusing transaction syntax with other database APIs

3. Given this transaction code snippet, what will be the final value of the 'count' field if the document initially has count = 5?

db.runTransaction(async (transaction) => {
  const docRef = db.collection('counters').doc('counter1');
  const doc = await transaction.get(docRef);
  if (!doc.exists) {
    transaction.set(docRef, { count: 1 });
  } else {
    const newCount = doc.data().count + 1;
    transaction.update(docRef, { count: newCount });
  }
});

medium

A. 6

B. 1

C. 5

D. 0

Solution

1. Step 1: Check if document exists

   The document exists with count = 5, so the else block runs.

2. Step 2: Calculate new count

   New count is 5 + 1 = 6, and transaction updates the document with this value.

3. Final Answer:

   6 -> Option A

4. Quick Check:

   Existing count + 1 = 6 [OK]

Hint: If doc exists, increment count by 1 [OK]

Common Mistakes:

• Assuming count resets to 1 even if doc exists
• Forgetting to add 1 to existing count
• Confusing set and update behavior

4. Identify the error in this transaction code snippet:

db.runTransaction(async (transaction) => {
  const docRef = db.collection('items').doc('item1');
  const doc = await transaction.get(docRef);
  const currentStock = doc.data().stock;
  if (currentStock > 0) {
    transaction.update(docRef, { stock: currentStock - 1 });
  }
});

medium

A. Missing check if document exists before accessing data

B. Using transaction.update instead of transaction.set

C. Not awaiting transaction.update call

D. Incorrect collection name syntax

Solution

1. Step 1: Check document existence

   The code accesses doc.data().stock without verifying if doc.exists, which can cause errors if doc is missing.

2. Step 2: Confirm other parts

   transaction.update is correct for partial update, awaiting update is not needed as transaction methods handle it, and collection name syntax is correct.

3. Final Answer:

   Missing check if document exists before accessing data -> Option A

4. Quick Check:

   Always check doc.exists before data [OK]

Hint: Always check doc.exists before reading data [OK]

Common Mistakes:

• Skipping doc.exists check causing runtime errors
• Confusing update with set methods
• Expecting to await transaction.update explicitly

5. You want to implement a transaction that increments a user's score only if the current score is less than 100. Which of the following code snippets correctly applies the transaction read-then-write pattern to achieve this?

hard

A. db.runTransaction(async (transaction) => {
const userRef = db.collection('users').doc('user1');
const doc = await transaction.get(userRef);
if (doc.data().score < 100) {
transaction.set(userRef, { score: doc.data().score + 1 });
}
});

B. db.runTransaction(async (transaction) => {
const userRef = db.collection('users').doc('user1');
const doc = await transaction.get(userRef);
if (doc.exists && doc.data().score < 100) {
transaction.update(userRef, { score: doc.data().score + 1 });
}
});

C. db.runTransaction(async (transaction) => {
const userRef = db.collection('users').doc('user1');
const doc = await transaction.get(userRef);
transaction.update(userRef, { score: 100 });
});

D. db.runTransaction(async (transaction) => {
const userRef = db.collection('users').doc('user1');
transaction.update(userRef, { score: 1 });
});

Solution

1. Step 1: Check document existence and condition

   db.runTransaction(async (transaction) => { const userRef = db.collection('users').doc('user1'); const doc = await transaction.get(userRef); if (doc.exists && doc.data().score < 100) { transaction.update(userRef, { score: doc.data().score + 1 }); } }); correctly checks if the document exists and if the score is less than 100 before updating.

2. Step 2: Verify update method and logic

   It uses transaction.update to increment the score by 1 only when condition is met, preserving existing data.

3. Final Answer:

   db.runTransaction(async (transaction) => { const userRef = db.collection('users').doc('user1'); const doc = await transaction.get(userRef); if (doc.exists && doc.data().score < 100) { transaction.update(userRef, { score: doc.data().score + 1 }); } }); -> Option B

4. Quick Check:

   Check exists + condition before update [OK]

Hint: Check doc exists and condition before update [OK]

Common Mistakes:

• Not checking if doc exists before reading data
• Using set instead of update causing overwrite
• Updating without condition or setting fixed value