Simulations
Lab
Four simulations from the essays. Each one is deterministic, runs in your browser, and is meant to be broken.
A retry storm
A three-second outage, five retries per request, four policies. Only one of them gets the server back.
FIG. 1 — A RETRY STORM
Stuck. The outage ended — the retries didn’t. Try “+ Retry budget”.
Retry policy
offered 0/s · goodput 0/s · retries 0% · status: HEALTHY
Lost messages and lost acks
The sender can't tell a lost message from a lost acknowledgement. Count the double charges.
FIG. 2 — LOST ACKS, DUPLICATE CHARGES
Behaviour
attempts 0 · applied 0 · duplicates 0 · lost 0 · deduped 0
Running…
The detection trade-off
Pick a timeout. Every setting trades false alarms for detection time.
FIG. 3 — DETECTION VERSUS FALSE ALARMS
Detector
Network jitter
false alarms 0 · detection +0.00 s
Utilization vs waiting
Push utilization past 90 % and watch the wait. Then bound the queue.
FIG. 4 — THE WAIT BEFORE THE WORK
Speed
utilization 0 % · mean wait 0.0 s · p99 0.0 s · queued 0 · rejected 0
Arrivals exceed capacity. This queue will grow until something runs out of memory.