Friendly Fire

"No one hires juniors anymore." Well, your company just did. Meet Tim. Tasked with fixing latency on the payment service, Tim made it "more robust" with a strict timeout and a 3x retry, so now every slightly-slow query times out and multiplies into three more. He's accidentally launched a DDoS against your own database, and you can't undo his timeout, only work around it. The Job: When the recovery spike hits, keep the retry cascade from taking the payment path down with it, with error and tail latency inside the SLA. Neutralize the storm Tim started. We'll deal with him on Monday.

Free to play, no account needed. A deterministic engine grades your design against this scenario's SLA - error rate, latency, and cost.