Problem context and objectives
Mission briefing
Lead systems engineer · Video Constellation
Design a global video platform supporting upload, processing, playback, recommendations, moderation, and creator analytics. State scope and defend tradeoffs.
The design must survive viewers 100M daily and uploads 500 hours/min. Every box must earn its place by satisfying a requirement or containing a failure.
How you win
- 1Trace one user action from request to durable outcome
- 2Connect every component to a stated requirement
- 3Explain the losing tradeoff, not only the chosen technology
Rules and pressure
- viewers: 100M daily
- uploads: 500 hours/min
- Resumable upload
- Asynchronous transcoding
Lesson 1 of 3
Live architecture trace
Video Constellation: request to outcome
LIVE EVENTsession
Creator sends “session” to Upload control. Separating control, asynchronous processing, and read-heavy playback creates clear failure and capacity boundaries.
viewers = 100M daily
Design a global video platform supporting upload, processing, playback, recommendations, moderation, and creator analytics. State scope and defend tradeoffs. Follow one real user action through the complete architecture; a component is useful only when you can explain the request, state, or failure it handles.