HLD-120·Caching & Edge
Easy · 500 ptsGlobal Anycast Authoritative DNS & Zone Store
Design a Route 53 / Cloudflare-style authoritative DNS lookup and zone-record propagation backend serving ultra-low-latency A/AAAA/CNAME answers.
Max p99
≤ 25 ms
Availability
≥ 99.5%
Budget
≤ $3,250
Functional Requirements
- FR-1GET /dns/resolve?name={domain_name} — Returns authoritative DNS record set with TTL.
- FR-2POST /dns/zones/{zone_id}/records — Updates DNS records and propagates to edge POPs.
- FR-3PATCH & DELETE /dns/resolve/{zone_id} — Updates, revokes, or deletes zone_id entries with bounded TTL or explicit cache/index invalidation.
- FR-4DNS resolution must sustain 99.5%+ availability during origin zone-store node failure.
Workload Profile
Baseline Queries30,000 Query RPS / 400 Zone Edit RPS
DDoS & Failover Surge78,000 Query RPS / 1,200 Write RPS
Active Working Set8 GB active zone records
Traffic DistributionExtreme skew on flagship domain_name records
Consistency Model
Eventual global POP propagation (< 10s) governed by record TTL; zone edits durably persisted.
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