The 37-minute Tuesday: anatomy of a cascading failure
A retry storm, a shared connection pool, and the graph everyone screenshotted. What actually happened.
Software, dissected weekly. Postmortems, protocol archaeology and the occasional strongly-held opinion about databases.
Read the latestA retry storm, a shared connection pool, and the graph everyone screenshotted. What actually happened.
The B-tree analogy everyone learns conceals the three behaviours that actually bite in production.
Distributed systems agree on almost nothing — except, mostly, the time. Here's the 40-year-old reason.
1curl -s https://hexline.dev/subscribe \2 -d email=you@example.com3# → 200 OK. one email, thursdays.4# → no tracking pixels. we checked ours. twice.“Every outage is a documentary about assumptions.”