HLD-213·Storage & Media
Medium · 1,000 ptsVideo Upload & Multi-Bitrate HLS Transcode Queue
Design a video upload metadata and transcode orchestration control plane dispatching chunked encoding tasks and serving studio readiness status.
Max p99
≤ 65 ms
Availability
≥ 99.5%
Budget
≤ $6,550
Functional Requirements
- FR-1POST /videos/{video_id}/jobs — Registers uploaded raw chunks and enqueues 360p/720p/1080p/4K worker jobs.
- FR-2GET /videos/{video_id}/status — Polled by creator studio UI for segment completion and publish state.
- FR-3DELETE /videos/{video_id}/jobs — Supports tenant retention TTL expiry, rule updates, or stream cleanup while keeping recent rollup caches fresh.
- FR-4Completed transcode state transitions must reflect immediately (read-after-write) and survive primary DB crash.
Workload Profile
Baseline Uploads24,000 Status Read RPS / 7,500 Job Write RPS
Weekend Creator Peak68,000 Read RPS / 24,000 Write RPS
Active Working Set18 GB active transcode DAG & manifest state
Fault ScenarioPrimary metadata DB crash mid-pipeline in Wave 3
Consistency Model
Read-after-write consistency required for job completion transitions; zero lost queued transcode tasks.
Solutions Locked
Sign in and either achieve AC or complete 3 official submissions on this question to inspect community diagrams and writeups.
Loading solutions...
Submission History (0)Select to replay
No submissions yet
Click Submit in the top bar to evaluate against all 7 judge cases and save each run here.
Click an item in Inventory above, or press B to add a component, double-click to name, C to connect.
Design Write-up
Write under ### Architecture for Diagram to take that up directly
Compulsory section · if not written yet, Diagram reads from the start of your write-up.
Architecture: required·FRs mentioned: 0/4·0 boxes · 0 edges
0 words