Distributed counting
Rate limiter service
- One token bucket
- One count for many limiters
- A limit per region
- When a limiter fails
- Final test
Protect a shared API from one noisy key. Start with one token bucket, then run several limiters without losing the count, split the limit between two regions, and keep the limits up when a limiter fails.
Final testThe batch key bursts in both regions, and box 1 in Europe restarts during the burst. Your final board runs once more with a new traffic seed.
Stage 4 of 4 · 5 parts given · 13,500 requests/s
Progress on this page stays on this device.