Newsletter
One email, every Tuesday
Latest posts
Every post here also goes out by email.
/w_300,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_300,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.
Written by Irina Dominte: Software Architect at Particular Software, Microsoft MVP, international speaker, and course author.
Browse all posts