---
title: 'How Instagram Handles Celebrities with 500M Followers Without Melting Their Servers'
source: 'https://youtube.com/watch?v=IMOmtAd2aUE'
video_id: 'IMOmtAd2aUE'
date: 2026-08-04
duration_sec: 78
---

# How Instagram Handles Celebrities with 500M Followers Without Melting Their Servers

> Source: [How Instagram Handles Celebrities with 500M Followers Without Melting Their Servers](https://youtube.com/watch?v=IMOmtAd2aUE)

## Summary

This video explains how social media platforms like Instagram handle the challenge of delivering posts from celebrities with hundreds of millions of followers without overwhelming their servers. It contrasts two fan-out strategies—write-time fan-out and read-time fan-out—and proposes a hybrid approach that balances load and latency.

### Key Points

- **The Problem with Massive Followers** [00:01] — A celebrity like Taylor Swift with 300 million followers creates a write storm if each post is pushed to every follower's cache, causing server load spikes and propagation delays.
- **Write-Time Fan-Out** [00:14] — For regular users, posts are precomputed into followers' feed caches, allowing fast reads. However, for celebrities, this triggers millions of cache writes per post, which is inefficient.
- **Hybrid Approach** [00:29] — Use write-time fan-out for regular users and special-case celebrities with read-time fan-out, where feeds are merged with celebrity posts at read time, keeping load flat.
- **Read-Time Fan-Out for Celebrities** [00:42] — When users load feeds, the system fetches celebrity posts separately and merges them, adding a small operation on top of cached feeds, keeping latency under 500ms.
- **No Universal Strategy** [00:57] — The right fan-out strategy depends on the data and system characteristics; there is no one-size-fits-all solution.

### Conclusion

The video emphasizes that system design requires nuanced trade-offs, and the hybrid fan-out approach effectively balances load and latency for celebrity posts.

## Transcript

Taylor Swift to post to her 300 million followers? One solution is to keep a cache for each user. The post gets pushed into each follower's cache immediately. Then we can read from that cache almost instantly when they load
the app. Great. Or until you have 300 million followers. A single post triggers 300 million cache writes at once. That write storm takes minutes to propagate and can spike server load to catastrophic levels. So,
let's use a hybrid approach. Regular users still get fan out on write. Their posts are precomputed into their followers feed caches. For celebrities, we can special case them in our system. When users load their feeds, they'll
celebrities they're following. This makes the right load stay flat no matter what Taylor does. The tradeoff is slightly more complex read logic, but feed latency stays under 500 milliseconds because the celebrity merge
is a small operation on top of an already cached feed. There's no universally correct fan out strategy. The right answer depends on the data your system is handling. That's the kind of nuance that separates a good system
design from a great. Like and follow us for more system design tips.
