A Queue Is a Shock Absorber, Not a Pump
Queue-Based Load Leveling absorbs spikes. It can't fix an average that is higher than what your consumers can process.
Load Shedding: Dropping Requests to Save Your System
Load shedding is the deliberate act of dropping requests to protect your system under overload. Most .NET teams don't have it.
/w_600,c_scale,q_auto/v1695118159/posts/twitter_tmpl.png)
REST APIs in Production: Pagination, HATEOAS, and the Patterns That Actually Matter (Part 3 of 3)
Part 3 of a REST API design series: pagination, HATEOAS, filtering and search, rate limiting, idempotency keys, and the practices that separate a demo API from a production one.
/w_600,c_scale,q_auto/v1695118159/posts/twitter_tmpl.png)
REST API Design: Resources, Versioning, and Auth That Hold Up (Part 2 of 3)
Part 2 of a REST API design series: naming resources so they don't need a manual, versioning without breaking clients, choosing an auth pattern, and structuring errors.
/w_600,c_scale,q_auto/v1695118159/posts/twitter_tmpl.png)
REST API Design: The Constraints and HTTP Semantics Everyone Skips (Part 1 of 3)
Part 1 of a REST API design series: what REST actually is, Fielding's six constraints, and the HTTP methods and status codes most APIs get subtly wrong.
What Happens to Outbox When the Database Goes Down?
Every outbox explanation assumes the broker is what breaks. Here is what actually happens when the database is the thing that goes away.
Compensation Is Not Rollback
Rollback is a database primitive. Distributed systems don't have one, and treating compensation as if they did is how workflows quietly break.
Your Idempotency Check Has a Race in It
Idempotency at rest is easy. Two retries arriving at the same moment is the case that breaks the version most teams wrote.
Hi! Welcome to my blog
One email, every Tuesday
.NET, messaging, and distributed systems - the trade-offs the docs leave out.
Form not loading? Subscribe here.
Let's connect
See it on dometrain
See it on dometrain
See it on dometrain
See it on Amazon