Design a video platform
A video platform is two systems joined at an object store. A write path that turns one large upload into thousands of small, pre-encoded segments, and a read path that is almost entirely a CDN, so the design questions are how to parallelise transcoding, how much storage the bitrate ladder costs, and what the CDN hit rate does to the bill.
What you'll be able to do
- Split the platform into an upload and processing path and a playback path, and size each one separately
- Compute the storage cost of a bitrate ladder per hour of video and per day of uploads
- Design transcoding as a DAG of segment-level jobs so a long video finishes in minutes, not hours
- Explain adaptive bitrate playback from manifests and segments, and why the CDN hit rate is the main cost lever
Before this: blob-storage-and-cdns, long-running-jobs
Log in to read the rest of this lesson
A video platform is two systems joined at an object store. A write path that turns one large upload into thousands of small, pre-encoded segments, and a read path that is almost entirely a CDN, so the design questions are how to parallelise transcoding, how much storage the bitrate ladder costs, and what the CDN hit rate does to the bill. This walkthrough runs about 27 minutes, with runnable code you can edit and re-run as you read. A new account gets 7 days of Pro free, no card required.
Log in to continueThe first module of every track is free to read on the web: see what's open in System design.