HLD-414·Rate Limiting
Expert · 2,000 ptsAnycast L7 WAF, Bot Reputation & Global Token-Bucket Edge
Design Cloudflare / Akamai’s global L7 Web Application Firewall evaluating JA4 TLS fingerprints, dynamic WAF rulesets, and distributed rate limits at 280k+ RPS.
Max p99
≤ 32 ms
Availability
≥ 99.6%
Budget
≤ $11,900
Functional Requirements
- FR-1POST /waf/evaluate — Checks compiled customer WAF ruleset, IP/JA4 reputation, and edge token bucket.
- FR-2POST /waf/rules/{zone_id} — Pushes emergency zero-day mitigation rules across global POPs.
- FR-3PATCH & DELETE /waf/evaluate/{zone_id} — Updates, revokes, or deletes zone_id entries with bounded TTL or explicit cache/index invalidation.
- FR-4Must sustain p99 <= 32ms during volumetric botnet floods and 8x origin analytics brownouts.
Workload Profile
Steady Edge Ingress95,000 WAF Check RPS / 10,000 Reputation/Counter Write RPS
Volumetric L7 Botnet Attack250,000 Check RPS / 32,000 Counter Write RPS
Active Working Set48 GB compiled zone WAF rulesets & hot ASN/JA4 scores
Latency GateUltra-strict inline edge budget p99 <= 32 ms
Consistency Model
Sub-2s eventual rule & reputation gossip across edge POPs; fail-open/cached fallback on origin brownout.
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