A resilient system isn't one that accepts every request. It's one that knows when accepting the next request would reduce the probability that existing requests succeed.
Situation:
A production checkout API suddenly receives far more traffic than its downstream payment, inventory, thread pools or DB connection pools can safely process.
Task:
Preserve useful customer transactions rather than accepting everything until latency explodes and the entire dependency chain becomes unhealthy.
Top comments (0)