Fan-out writes pattern in Firebase - Step-by-Step Execution

Process Flow - Fan-out writes pattern

Client sends data to write

↓

Server receives data

↓

Write data to main location

↓

Write same data to multiple locations

↓

Confirm all writes succeed

↓

Return success

The fan-out writes pattern copies data to multiple places in the database at once to keep data consistent and improve read speed.

Execution Sample

Firebase

const updates = {};
updates['/posts/post1'] = postData;
updates['/user-posts/user1/post1'] = postData;
return firebase.database().ref().update(updates);

This code writes the same post data to two places in the database at once using a single update call.

Process Table

Step	Action	Data Location	Data Written	Result
1	Prepare updates object	N/A	{'/posts/post1': postData, '/user-posts/user1/post1': postData}	Ready to write
2	Call update() with updates	Root	Multiple paths	Start atomic write
3	Write to /posts/post1	/posts/post1	postData	Success
4	Write to /user-posts/user1/post1	/user-posts/user1/post1	postData	Success
5	All writes complete	N/A	N/A	Return success to client

💡 All writes succeed, update() completes atomically

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 5
updates	{}	{'/posts/post1': postData, '/user-posts/user1/post1': postData}	Same	Same

Key Moments - 3 Insights

Why do we write the same data to multiple locations?

Writing to multiple locations keeps data consistent and allows faster reads from different parts of the app, as shown in steps 3 and 4 of the execution_table.

What happens if one write fails during update()?

The update() call is atomic, so if any write fails, none are applied. This ensures data consistency, as implied in the exit_note.

Why use a single update() call instead of multiple separate writes?

A single update() call ensures all writes happen together atomically, avoiding partial updates and keeping data consistent, as shown in steps 2 to 5.

Visual Quiz - 3 Questions

Look at the execution_table, what data is written at step 3?

A postData to /posts/post1

B postData to /user-posts/user1/post1

C updates object to root

D No data written

💡 Hint

Check the 'Data Location' and 'Data Written' columns in step 3 of execution_table

At which step does the client receive confirmation that all writes succeeded?

A Step 2

B Step 5

C Step 4

D Step 1

💡 Hint

Look at the 'Result' column for when the update completes successfully

If the update() call was split into two separate writes, what risk increases?

A No risk, same behavior

B Writes become atomic automatically

C Data might be partially written causing inconsistency

D Writes happen faster

💡 Hint

Refer to key_moments about atomicity and partial writes

Concept Snapshot

Fan-out writes pattern:
- Write same data to multiple database paths
- Use a single atomic update() call
- Keeps data consistent across locations
- Improves read performance
- Avoids partial updates

Full Transcript

The fan-out writes pattern in Firebase means writing the same data to multiple places in the database at once. This is done by creating an updates object with all target paths and data, then calling update() once. This ensures all writes happen together atomically, so either all succeed or none do. This keeps data consistent and allows faster reads from different parts of the app. The execution steps show preparing the updates, calling update(), writing to each location, and finally confirming success. Key points include why multiple writes are needed, atomicity of update(), and risks of separate writes. This pattern is important for keeping data synchronized and reliable.

Practice

1. What is the main purpose of the fan-out writes pattern in Firebase?

easy

A. To save the same data in multiple places at once for faster reads

B. To delete data from multiple locations simultaneously

C. To back up data to an external server

D. To encrypt data before saving it

Solution

1. Step 1: Understand fan-out writes concept

   Fan-out writes save identical data in many database locations at once.

2. Step 2: Identify the benefit

   This helps apps read data faster and simpler by having data ready where needed.

3. Final Answer:

   To save the same data in multiple places at once for faster reads -> Option A

4. Quick Check:

   Fan-out writes = save data in many places [OK]

Hint: Fan-out writes duplicate data to speed up reading [OK]

Common Mistakes:

• Thinking fan-out writes delete data
• Confusing fan-out with backup
• Assuming fan-out encrypts data

2. Which Firebase method is used to perform a fan-out write to multiple paths atomically?

easy

A. firebase.database().remove()

B. firebase.database().set()

C. firebase.database().push()

D. firebase.database().update()

Solution

1. Step 1: Recall Firebase write methods

   set() writes to one location, push() adds new child, remove() deletes data.

2. Step 2: Identify atomic multi-path update

   update() can write to many paths at once atomically, perfect for fan-out writes.

3. Final Answer:

   firebase.database().update() -> Option D

4. Quick Check:

   Multi-path atomic write = update() [OK]

Hint: Use update() for atomic multi-path writes [OK]

Common Mistakes:

• Using set() which overwrites one path only
• Using push() which adds new child, not multi-path
• Using remove() which deletes data

3. Given this update object for fan-out writes:

{
  '/posts/post1': { title: 'Hello' },
  '/user-posts/user1/post1': { title: 'Hello' }
}

What happens when you call firebase.database().ref().update(updateObject)?

medium

A. Data is saved only at '/posts/post1'

B. Data is saved at both '/posts/post1' and '/user-posts/user1/post1' atomically

C. Data is not saved due to syntax error

D. Data is saved only at '/user-posts/user1/post1'

Solution

1. Step 1: Understand update() with multiple paths

   Update accepts an object with multiple paths as keys and writes data atomically to all.

2. Step 2: Analyze given updateObject

   It has two paths: '/posts/post1' and '/user-posts/user1/post1', both with same data.

3. Step 3: Predict behavior

   Calling update() writes data to both paths at once, ensuring consistency.

4. Final Answer:

   Data is saved at both '/posts/post1' and '/user-posts/user1/post1' atomically -> Option B

5. Quick Check:

   update() writes all paths atomically [OK]

Hint: update() writes all paths in one call atomically [OK]

Common Mistakes:

• Thinking update() writes only one path
• Confusing update() with set()
• Assuming syntax error in object

4. You wrote this fan-out update object:

{
  '/posts/post1': { title: 'Hello' },
  '/posts/post1': { author: 'Alice' }
}

What is the problem with this update object?

medium

A. Duplicate keys cause only the last one to be saved

B. Firebase rejects duplicate keys with an error

C. Data will be merged correctly without issues

D. The update will only save the first key

Solution

1. Step 1: Identify duplicate keys in object

   The object has two entries with the same key '/posts/post1'.

2. Step 2: Understand JavaScript object behavior

   Duplicate keys in an object overwrite previous ones; only the last remains.

3. Step 3: Predict Firebase update behavior

   Firebase receives only the last key-value pair, so only { author: 'Alice' } is saved.

4. Final Answer:

   Duplicate keys cause only the last one to be saved -> Option A

5. Quick Check:

   Duplicate keys overwrite previous in objects [OK]

Hint: No duplicate keys in update object; last wins [OK]

Common Mistakes:

• Expecting Firebase to merge duplicate keys
• Thinking Firebase throws error on duplicates
• Assuming first key is saved instead of last

5. You want to save a new comment both under /comments/comment1 and also under /post-comments/post1/comment1 using fan-out writes. Which update object correctly implements this pattern?

hard

A. { '/comments/comment1': { text: 'Nice!' }, '/comments/comment1': { text: 'Nice!' } }

B. { '/comments/comment1': { text: 'Nice!' }, '/post-comments/post1': { text: 'Nice!' } }

C. { '/comments/comment1': { text: 'Nice!' }, '/post-comments/post1/comment1': { text: 'Nice!' } }

D. { '/comments/comment1': { text: 'Nice!' }, '/post-comments/post1/comment1': 'Nice!' }

Solution

1. Step 1: Understand fan-out write structure

   Each path key must be a full path string to the exact location, and values must be objects with data.

2. Step 2: Analyze each option

   A: duplicate keys for same path; only one location updated.
   B: distinct full paths to both locations with data objects; correct.
   C: second path too shallow ('/post-comments/post1'), places text directly under post1, missing /comment1.
   D: string instead of object at second path.

3. Step 3: Choose correct update object

   { '/comments/comment1': { text: 'Nice!' }, '/post-comments/post1/comment1': { text: 'Nice!' } } correctly writes the comment data to both paths atomically.

4. Final Answer:

   { '/comments/comment1': { text: 'Nice!' }, '/post-comments/post1/comment1': { text: 'Nice!' } } -> Option C

5. Quick Check:

   Full paths as keys with data objects = correct fan-out [OK]

Hint: Use full paths as keys with data objects for fan-out [OK]

Common Mistakes:

• Using duplicate keys in update object
• Nesting data instead of using full path keys
• Assigning string instead of object as value