One email, every Tuesday
Every post here also goes out by email.
Rollback is a database primitive. Distributed systems don't have one, and treating compensation as if they did is how workflows quietly break.
Idempotency at rest is easy. Two retries arriving at the same moment is the case that breaks the version most teams wrote.
Your data disagreeing with itself isn't a bug. It's a trade-off. What eventual consistency guarantees, where you're already relying on it, and how to design for it instead of getting bitten by it.
A practical guide to designing long-running business processes with the Saga pattern - covering orchestration vs choreography, compensating transactions, timeouts, and observability.
How to keep Claude Code agents and skills out of shared repos using a dedicated config repo and symlinks.
Written by Irina Dominte: Software Architect at Particular Software, Microsoft MVP, international speaker, and course author.
Browse all posts