Backpressure is the concept your system is missing
When a fast producer meets a slow consumer, something has to give. Deciding what, in advance, is the whole discipline.
tech, developers, and the code underneath
17 pieces tagged reliability,
from March 10, 2025 to July 3, 2026.
When a fast producer meets a slow consumer, something has to give. Deciding what, in advance, is the whole discipline.
The most common way a small incident becomes a large one is a retry policy written without thinking about aggregate behavior.
It has no type system, no tests, no review, and it causes a disproportionate share of outages.
The bug that happens once a week and never in staging. A systematic approach to the class of problem everyone handles badly.
Most tracing deployments produce beautiful waterfalls nobody opens. The difference is three implementation details.
A month of synchronized global demand across three countries, sixteen cities, and every streaming platform at once.
Most scaling problems are solved by making something asynchronous. Most reliability problems are caused by doing it badly.
Game days, failure injection, and the specific reason your untested runbook is wrong.
At some point your telemetry bill exceeded your compute bill and nobody noticed. Here's how to fix it without going blind.
Token bucket, leaky bucket, fixed window, sliding window. They fail differently and the differences matter.
If your rotation is painful, that's information about your architecture, not about your people's resilience.
Availability percentages are a compliance artifact. Here's what to measure if you want to know whether users are having a bad time.