Fan-out on write vs fan-out on read in HLD - When to Use Which

The Big Idea

What if your favorite app could instantly show new posts without crashing or delays?

The Scenario

Imagine you run a social media app where millions of users post updates. When a user posts, you must send that update to all their followers. Doing this manually means sending messages to each follower one by one every time someone posts.

The Problem

This manual way is slow and clogs the system because sending updates to thousands or millions of followers at post time takes too long. It also risks errors and delays, making users wait to see new posts.

The Solution

Fan-out on write and fan-out on read are smart ways to handle this. Fan-out on write sends updates to followers immediately when a post happens, so reading is fast. Fan-out on read keeps posts in one place and sends them to followers only when they check, saving work upfront but making reads slower.

Before vs After

✗ Before

for follower in followers:
    send_update(post, follower)

✓ After

Fan-out on write: store post in each follower's feed at write time
Fan-out on read: store post once, fetch for followers when they read

What It Enables

These approaches let apps handle millions of users smoothly by balancing speed and resource use for posting and reading updates.

Real Life Example

Twitter uses fan-out on write to quickly show tweets to followers, while Instagram uses fan-out on read to save storage and compute when showing posts.

Key Takeaways

Manual sending to followers is slow and error-prone.

Fan-out on write pushes updates early for fast reads.

Fan-out on read delays pushing updates to save resources.

Practice

1. What is the main advantage of using fan-out on write in system design?

easy

A. Simpler read logic by fetching data on demand

B. Faster read operations by duplicating data during write

C. Reduced storage usage by avoiding data duplication

D. Faster write operations by delaying data duplication

Solution

1. Step 1: Understand fan-out on write behavior

   Fan-out on write duplicates data to multiple places during the write operation.

2. Step 2: Analyze impact on read speed

   This duplication allows reads to be faster because data is already pre-distributed and ready to access.

3. Final Answer:

   Faster read operations by duplicating data during write -> Option B

4. Quick Check:

   Fan-out on write = Faster reads [OK]

Hint: Fan-out on write means write duplicates data for fast reads [OK]

Common Mistakes:

• Confusing fan-out on write with fan-out on read
• Thinking fan-out on write reduces storage
• Assuming writes are faster with fan-out on write

2. Which of the following best describes fan-out on read?

easy

A. Data is compressed during write to save storage

B. Data is duplicated during write to speed up reads

C. Data is cached permanently to reduce read latency

D. Data is fetched and combined during read to keep writes fast

Solution

1. Step 1: Define fan-out on read

   Fan-out on read means data is not duplicated during write but fetched from multiple sources during read.

2. Step 2: Understand write speed impact

   This keeps writes fast because no extra duplication work is done during write time.

3. Final Answer:

   Data is fetched and combined during read to keep writes fast -> Option D

4. Quick Check:

   Fan-out on read = Fast writes, complex reads [OK]

Hint: Fan-out on read delays data gathering until read time [OK]

Common Mistakes:

• Mixing fan-out on read with fan-out on write
• Assuming fan-out on read duplicates data during write
• Confusing caching with fan-out on read

3. Consider a system using fan-out on write. If a user updates their profile, what happens during the write operation?

medium

A. The update is duplicated to multiple storage locations immediately

B. The update is written once and read fetches combine data later

C. The update is cached temporarily and written later asynchronously

D. The update is compressed and stored in a single location

Solution

1. Step 1: Recall fan-out on write behavior

   Fan-out on write duplicates data during the write operation to multiple places.

2. Step 2: Apply to user profile update

   When a user updates their profile, the system writes the update to all relevant storage locations immediately.

3. Final Answer:

   The update is duplicated to multiple storage locations immediately -> Option A

4. Quick Check:

   Fan-out on write = Immediate duplication on write [OK]

Hint: Fan-out on write duplicates data immediately on update [OK]

Common Mistakes:

• Thinking update is written once and combined later
• Confusing caching with fan-out on write
• Assuming asynchronous write in fan-out on write

4. A system using fan-out on read is experiencing slow response times. What is a likely cause?

medium

A. Writes are slow due to data duplication

B. Storage is overloaded due to duplicated data

C. Reads are slow because data is fetched from multiple sources on demand

D. Data is compressed causing decompression delays

Solution

1. Step 1: Understand fan-out on read read behavior

   Fan-out on read fetches data from multiple sources during read, which can add latency.

2. Step 2: Analyze slow response cause

   Because reads combine data on demand, slow response times are likely due to this complex read process.

3. Final Answer:

   Reads are slow because data is fetched from multiple sources on demand -> Option C

4. Quick Check:

   Fan-out on read = Slow reads if sources are many [OK]

Hint: Fan-out on read can cause slow reads due to multiple fetches [OK]

Common Mistakes:

• Blaming slow writes in fan-out on read
• Assuming storage overload in fan-out on read
• Confusing compression delays with fan-out issues

5. You are designing a social media feed system. Which approach is better if you want instant feed updates but can tolerate higher storage costs?

hard

A. Fan-out on write to duplicate feed data for fast reads

B. Fan-out on read to keep writes fast and storage low

C. Use caching only without fan-out

D. Compress data on write to save storage

Solution

1. Step 1: Identify system needs

   Instant feed updates require fast reads with up-to-date data.

2. Step 2: Match approach to needs

   Fan-out on write duplicates feed data during write, enabling fast reads and instant updates but uses more storage.

3. Step 3: Evaluate other options

   Fan-out on read delays data gathering to read time, causing slower reads. Caching alone may not guarantee instant updates. Compression saves storage but slows access.

4. Final Answer:

   Fan-out on write to duplicate feed data for fast reads -> Option A

5. Quick Check:

   Instant updates + higher storage = Fan-out on write [OK]

Hint: Instant reads with more storage? Choose fan-out on write [OK]

Common Mistakes:

• Choosing fan-out on read for instant updates
• Ignoring storage cost impact
• Assuming caching replaces fan-out needs