Exponential Backoff & Jitter Visualizer
Simulate retry delay schedules with and without jitter, and see how client herds pile onto the same tick without randomization.
Exponential Backoff & Jitter
Compare full, equal, and decorrelated jitter retry schedules — see how spreads avoid thundering herds.
AWS architecture blogs recommend full jitter for most cases: random(0, min(cap, base * 2^attempt)). Decorrelated: min(cap, random(base, prev*3)).
Strategies
| Strategy | Formula (simplified) |
|---|---|
| No jitter | min(cap, base * multiplier^attempt) |
| Full jitter | random(0, exp) |
| Equal jitter | exp/2 + random(0, exp/2) |
| Decorrelated | min(cap, random(base, prev * 3)) |
Full jitter is usually the best default for widely distributed clients hitting the same dependency.
