
The Health Check That Watched the Wrong Thing
The last post ended on a promise: background workers fall into the same correlated-failure trap as request services, from a different angle. This is that angle, and it starts one level earlier: a heal
Engineering investigations into how production systems behave, break, and get put back together. Reliability, performance, and the architecture decisions behind them, written as postmortems rather than tutorials. Backend with both feet in the infrastructure (AWS, CI/CD, distributed systems), mostly language-agnostic, with the trade-offs spelled out.

The last post ended on a promise: background workers fall into the same correlated-failure trap as request services, from a different angle. This is that angle, and it starts one level earlier: a heal
Your database dropped out for a few minutes. Your health check turned that into a full outage. That's not a hypothetical situation I made up for effect. It happened to us twice, in two different shape

I was implementing a feature where the session container would track a lastActivity timestamp, updated on every authenticated request. Standard stuff. I wrote it, tested it locally with curl, and noti

You push a critical hotfix, switch branches—and your CI is still running 30 minutes later. In my current project, our backend pipeline ran across a massive monorepo (~7,000 unit, ~600 integration, ~15
