Original caption
One upload in. A billion plays out. Nine boxes. That's the whole design. 📤 SOMEONE UPLOADS Creator → upload service → raw file. The original gets kept exactly once, untouched. You never throw it away, because every future format gets made from it. The upload service also writes a row in the VIDEO DB — title, owner, is it ready. That row exists immediately. It's why the page loads before the video plays. Then the converters do the real work: cut the file into small pieces and make every piece in 5 sizes. 📦 THE CHUNK STORE Every piece, in every size. Written once. Everyone shares it. This is the box both halves touch. Converters write it, the CDN copies from it. Nothing else crosses the line. ▶️ EVERYONE WATCHES Viewer → web page → CDN → player. The web page gets the title and the list of available sizes. The CDN holds copies close to you. The player grabs one piece at a time and switches size when your network dips. 👀 The line most people miss: VIDEO DB runs straight down to the web page, skipping conversion entirely. That's why a fresh upload opens instantly but only offers 360p for the first few minutes. The row is ready long before the pieces are. THE RULE: upload is slow and happens once. Play is fast and never stops. You spend minutes of work per video so a billion views each cost almost nothing. The failure mode: drawing one box labelled "transcode." That box is a split, a fleet, and a stitch — and it's the only part of this system that's actually hard. 📸 Screenshot this before your next system design interview. Follow @hackproduct ⚡ . . #systemdesign #systemdesigninterview #softwareengineering #youtube #backenddevelopment