HLD-125·Storage & Media
Easy · 500 ptsStatic Site Atomic Deployment & Edge Asset Router
Design a Vercel/Netlify-style immutable static deployment router mapping custom domains to content-addressed asset bundles with instant atomic rollbacks.
Max p99
≤ 38 ms
Availability
≥ 99.5%
Budget
≤ $3,350
Functional Requirements
- FR-1GET /serve/{site_domain}/{asset_path} — Resolves active deployment ID and serves immutable asset.
- FR-2POST /deployments/{site_domain}/promote — Atomically points domain alias to a new build manifest.
- FR-3Retention & Lifecycle (site_domain) — Enforces TTL retention windows, deduplication, or archival compaction without blocking live reads or writes.
- FR-4Must sustain traffic surges when origin blob storage suffers 5x gray latency.
Workload Profile
Baseline Requests28,000 Asset Read RPS / 500 Deploy Write RPS
Product Launch Spike82,000 Read RPS / 1,500 Write RPS
Active Working Set18 GB hot HTML/JS/CSS bundles
Traffic DistributionStrong Zipfian skew on viral landing site_domain hosts
Consistency Model
Eventual edge alias invalidation (< 3s) acceptable; content-hashed assets are immutable.
Relevant practice for
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