Every timeout must be shorter than the one in front
The claim Most cascading outages are not caused by a component failing. They are caused by a component being slow while every timeout in the stack is longer than the one upstream o...
Read articleInsights
Engineering notes, infrastructure deep dives and practical guides from the Exotecho team.
The claim Most cascading outages are not caused by a component failing. They are caused by a component being slow while every timeout in the stack is longer than the one upstream o...
Read articleThe claim Free-text log lines without a correlation identifier are not diagnostic data. They are a diary. During an incident you cannot answer the only question that matters — what...
Read articleThe claim Any call to a third-party service inside a request handler makes that service a hard dependency of your application. Sending mail synchronously means your order confirmat...
Read articleThe claim On a typical content or commerce site, images account for the majority of transferred bytes — usually 55% to 75% — and the fix is a build step you configure once, not a f...
Read articleThe claim A migration that changes the shape of a table and the code that reads it in the same deploy cannot be rolled back. During the seconds or minutes when old and new applicat...
Read articleThe claim An endpoint that returns 200 unconditionally is worse than having no health check at all. It converts a loud failure into a silent one: your load balancer keeps routing t...
Read articleThe claim Below roughly a million searchable rows, PostgreSQL's built-in full-text search is not a stopgap. It is the correct answer, and adding a separate search cluster at that s...
Read articleThe claim For a marketing site, a product catalogue, a booking flow, or an internal dashboard with a few hundred users, server-rendered HTML with a modest amount of JavaScript will...
Read article