正在加载视频...

视频加载失败

To understand how live streaming works, understand HLS (HTTP Live Streaming.) A summary from Ashutosh Agrawal who architected a live streaming system serving 32M concurrent streams at peak:

12,593 次观看 • 1 年前 •via X (Twitter)

3 条评论

Gergely Orosz 的头像
Gergely Orosz1 年前

Full episode: YouTube: Spotify: Apple: Summary and transcript:

Zibu 的头像
Zibu1 年前

@theprogrammerin This podcast is more about architecture on a very high level and not about the actual engineering behind video streaming.

Aviv Dozorets 🎗️ 的头像
Aviv Dozorets 🎗️1 年前

@theprogrammerin ~10 years ago there was a "format war" between HLS (backed by apple), HDS (backed by adobe), silverlight (backed by msft) and mpeg-dash (community effort). There were even companies that sold ISP DPI tools to remove ability for high-level (4k) video streaming.

相关视频

In May 2023, a live streaming world record was set with 32 million concurrent viewers watching the finale of the IPL cricket game. How was this system built? Ashutosh Agrawal was the architect behind this system, and he walks us through how live streaming at scale works, how the system was built and tested, and other interesting learnings. Watch or listen: • YouTube: • Spotify: • Apple: --- Brought to you by our wonderful sponsors: • WorkOS — The modern identity platform for B2B SaaS • CodeRabbit — Cut code review time and bugs in half (use the code PRAGMATIC to get one month free) • Augment Code — AI coding assistant that pro engineering teams love --- Three of my biggest takeaways: 1. The architecture behind live streaming systems is surprisingly logical. In the episode, Ashutosh explains how the live streaming system works, starting from the physical cameras on-site, through the production control room (PCR), streams being sliced-and-diced, and the HLS protocol (HTTP Live Streaming) used. 2. There are a LOT of tradeoffs you can play with when live streaming! The tradeoffs between server load, latency, server resources vs client caching are hard decisions to make. Want to reduce the server load? Serve longer chunks to clients, resulting in fewer requests per minute, per client… at the expense of clients potentially lagging more behind. This is just one of many possible decisions to make. 3. “Game day” is such a neat load testing concept. The team at Jio would simulate “game day” load months before the event. They did tell teams when the load test will start: but did not share anything else! Preparing for a “Game day” test is a lot of work, but it can pay off to find parts of the system that shutter under extreme load. See more takeaways and a summary here: Thanks Ashutosh for all these behind-the-scene details!

Gergely Orosz

50,597 次观看 • 1 年前