Design Live-Event Streaming

"Design live-event streaming" is the freshest and hardest prompt in the Netflix loop. It usually shows up as "design live streaming for a boxing match or an NFL game at Netflix scale." It builds directly on the on-demand video design. Come in assuming the interviewer knows you can stream a movie and wants to see what you do when the feed is happening right now. The catalog still browses, the encode pipeline still runs, and the CDN still delivers. Every one of them gets reshaped by three facts about live. The whole audience arrives in the same minute. There is no pre-encoded file to lean on, because the title is being created as it streams. And there is no second take, because a live moment that drops is gone.

Anchor on the numbers first. A marquee live event pulls on the order of tens of millions of concurrent devices. The headline case Netflix now plans for is roughly 100 million devices joining a single stream inside the first minute. Each device wants a few megabits per second of video. So the aggregate egress runs into the tens of terabits per second, and all of it lands on one stream instead of spreading across a catalog. Call out the join spike early. The load that decides this design is not steady-state viewing. It is the wall of people who all press play the instant the main event starts.

The Netflix angle

This is the newest prompt in the loop, and it rewards judgment over recall. Netflix's Live Origin work powers the boxing and NFL streams it now runs, and it's recent enough that nobody expects you to recite the internal stack. The whole test is whether you see why the on-demand playbook bends under live. Proactive fill is gone. The join is a thundering herd. A one-shot event makes redundancy non-negotiable. Spot those three shifts yourself and the rest of the design follows.