Why Fan-out writes pattern in Firebase? - Purpose & Use Cases

The Big Idea

What if your app could share updates instantly with everyone, without missing a beat?

The Scenario

Imagine you have a social app where a user posts a message, and you want that message to appear instantly on all their friends' feeds.

If you try to update each friend's feed one by one manually, it feels like sending a letter to each friend separately every time you post.

The Problem

Manually updating each friend's feed is slow and prone to mistakes.

If the app crashes halfway, some friends won't see the post.

It also wastes time and resources, making the app feel sluggish.

The Solution

The fan-out writes pattern solves this by automatically copying the post to all friends' feeds in one go.

This way, the app updates everyone efficiently and reliably, like sending a group message instead of many letters.

Before vs After

✗ Before

for friend in friends:
  database.update(friend.feed, new_post)

✓ After

database.update({friend1.feed: new_post, friend2.feed: new_post, /* ... */})

What It Enables

This pattern makes real-time updates fast and consistent across many users, improving user experience and app reliability.

Real Life Example

When you post a photo on a social network, fan-out writes ensure all your followers see it quickly in their feeds without delay or missing updates.

Key Takeaways

Manual updates to many places are slow and risky.

Fan-out writes copy data efficiently to multiple locations at once.

This improves speed, reliability, and user satisfaction.

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