System Design
Intermediate
Pro
Rate Limiting
Choose the right algorithm, enforce it across a fleet, and design a rate limiter that survives its own failures
25 min read
12 views
Compare token bucket, leaky bucket, fixed window, sliding log and sliding window counter with worked numbers, then design a distributed rate limiter on Redis, handle 429 responses correctly, and reason about fail-open versus fail-closed when the limiter itself is down.
Practice questions (5)
-
View →
Fixed Window Boundary Burst
Intermediate · Free -
View →
Distributed Rate Limiting Race Condition
Advanced -
View →
Configuring a Token Bucket for Burst and Sustained Rate
Intermediate -
View →
Redis Outage: Fail-Open vs Fail-Closed
Advanced -
View →
Rate Limiting vs Load Shedding vs Circuit Breaking
Intermediate