CoursesSystem Design Case Studies
The Video Platform
Uploads that become a dozen renditions, a backlog that must not eat the fleet, storage tiers priced by how often a video is watched, delivery that pays per byte, abuse that costs real money, and the whole design under a viral clip.
- Lessons
- 5
- Exercises
- 29
- Minutes
- 34
- 1
The Transcoding Pipeline
After this lesson you can size a transcoding fleet from upload rate and work per upload, split a long job into segments that fail and retry independently, and bound the backlog so a burst of uploads does not stall the platform.
DebugCode orderMultiple choiceShort answer - 2
What a View Costs
After this lesson you can put a number on storing and serving a video, tier storage by how often a video is watched, and decide which renditions to keep for a video nobody watches.
DebugMultiple choiceShort answer - 3
Delivery, and the Bytes Nobody Should Get
After this lesson you can serve segments through the CDN with signed URLs, stop a scraper from downloading the catalogue at your expense, and rate-limit uploads by the key that stops abuse without blocking a busy studio.
DebugMultiple choiceShort answer - 4
Checkpoint: Video VariationsCheckpoint
The same design under different numbers: a lecture platform, a short-clip app, and a private archive.
DebugMultiple choiceShort answer - 5
Boss: The Video PlatformBoss
The whole design: the question, the numbers, the pipeline, the tiers and the gate, the viral clip, the backlog that idled the fleet, the revised pipeline, and the tradeoff you defend.
Code orderMultiple choiceShort answerTrace