A two-second dependency should cost you latency, not three services. The mechanics are arithmetic: Little's law plus retry amplification. The fix is a budget, not a ban.
an account raises the per-topic limit · no card
← Incident Response & Production Debugging / 15
hard★ EssentialNewGoogleNetflixUber
One dependency slowed down and three services fell over completely. Walk me through the mechanics, then how you stop the next one.
A two-second dependency should cost you latency, not three services. The mechanics are arithmetic: Little's law plus retry amplification. The fix is a budget, not a ban.
Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.
UP NEXT ON YOUR JOURNEY
Next in this trackYour last three incidents had nearly identical action items. What is broken about your post-mortem process?Next in this trackA VM rebooted after a storage change and dropped into emergency mode. Talk me through the recovery and what you check first.Next in this trackkubectl takes ten seconds, operator leader elections flap, and etcd fsync latency is the only red metric. What now?
DISCUSSION · 0
Nothing here yet. Say how you would answer it.