The five resilience patterns that stop a cascading failure
How one slow secondary dependency takes down the whole system in ninety seconds, and the five patterns that prevent it.
Archive · Engineering
8 articles published in this category. Use the search to narrow by tag, or go back to the full archive.
How one slow secondary dependency takes down the whole system in ninety seconds, and the five patterns that prevent it.
You need to debit one account and credit another, and they live in different databases. The two patterns that solve it in practice, and what to avoid.
CAP is the most quoted and most badly stated theorem in distributed computing. This article fixes the statement and shows the vocabulary you actually use day to day.
Sharding is the most irreversible decision in a data system. This is the guide to deciding whether you need it and, if you do, how to pick the key.
How an index works on the inside, why column order decides everything, and how to read an execution plan to know what to do.
Adding a cache is easy. The hard part is living with the four consequences it creates, and all four have known solutions.
Your average latency is lying to you. The three concepts that turn 'the system is slow' into a sentence with a number, an endpoint and a percentile.
Every gateway redelivers webhooks. If your handler is not idempotent, you will find out on the day the same sale gets counted three times.
Talk to me
No form and no mailing list. If you disagree with something I wrote, or want to tell me how you solved it, the conversation goes straight to me.