Fan-out writes pattern in Firebase - Mini Project: Build & Apply

Fan-out Writes Pattern in Firebase

📖 Scenario: You are building a simple social media app where users can post messages. To make the app fast and scalable, you want to store each post in two places: under the user's posts and in a global posts list.This is called the fan-out writes pattern, where one write operation updates multiple places in the database at once.

🎯 Goal: Build a Firebase Realtime Database update that writes a new post to both the user's posts and the global posts list in a single operation.

📋 What You'll Learn

Create a JavaScript object called postData with the exact keys author and content and their values.

Create a JavaScript object called updates that will hold the paths to update in the database.

Use the updates object to set the new post under /posts/<postId> and under /user-posts/<userId>/<postId>.

Add the final call to firebase.database().ref().update(updates) to perform the fan-out write.

💡 Why This Matters

🌍 Real World

Fan-out writes are used in real apps to keep data duplicated in multiple places for fast reads and easy queries.

💼 Career

Understanding fan-out writes is important for Firebase developers to build scalable and efficient real-time applications.

1

Create the post data object

Create a JavaScript object called postData with the keys author set to 'user123' and content set to 'Hello Firebase!'.

Firebase

// Create the postData object with author and content
// Your code here

Hint

Use const postData = { author: 'user123', content: 'Hello Firebase!' };

2

Create the updates object with paths

Create a JavaScript object called updates. Add two keys: `/posts/post1` and `/user-posts/user123/post1`. Set both keys to the value postData.

Firebase

const postData = {
  author: 'user123',
  content: 'Hello Firebase!'
};
// Create the updates object with two paths set to postData
// Your code here

Hint

Use const updates = { '/posts/post1': postData, '/user-posts/user123/post1': postData };

3

Write the fan-out update call

Call firebase.database().ref().update(updates) to perform the fan-out write using the updates object.

Firebase

const postData = {
  author: 'user123',
  content: 'Hello Firebase!'
};

const updates = {
  '/posts/post1': postData,
  '/user-posts/user123/post1': postData
};
// Call firebase.database().ref().update(updates) to write data
// Your code here

Hint

Use firebase.database().ref().update(updates); to write all paths at once.

4

Add a comment explaining the fan-out pattern

Add a comment above the update call explaining that this is a fan-out write updating multiple paths in one operation.

Firebase

const postData = {
  author: 'user123',
  content: 'Hello Firebase!'
};

const updates = {
  '/posts/post1': postData,
  '/user-posts/user123/post1': postData
};

// Your comment here
firebase.database().ref().update(updates);

Hint

Add a comment like // Fan-out write: update multiple database paths in one atomic operation above the update call.

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