Video streaming pipeline
Upload → transcode fan-out across renditions → fan-in packaging → origin → multi-CDN delivery with health-scored failover.
What this design does
Video is a pipeline problem wearing a media costume: one master file fans out to parallel transcode stages (1080p, 720p, audio, captions — pipes and filters, each independently restartable), fans back in at the packager that won't cut a manifest until every rendition exists, and lands on an origin that only CDNs may touch. Two CDNs, health-scored, mean a provider's bad day costs you a failover, not an outage.
The patterns it composes
- Pipes and filters — each transcode stage is stateless and restartable in isolation
- Fan-out / fan-in (wait-for-all) — renditions run in parallel; the manifest waits for every one
- CDN edge caching — viewers hit the edge; the origin sees only cache misses
- Multi-CDN origin failover — player-side health scoring shifts traffic between providers
- Queue-based job orchestration — transcode jobs survive worker crashes and retry cleanly
Import it, attach your own numbers, and verify the design against failures — or read the engineering notes.