Async Does Not Mean Scalable
async/await frees threads but doesn't reduce work. Message queues move the bottleneck, they don't remove it. Here's what actually limits throughput in .NET systems.
async/await frees threads but doesn't reduce work. Message queues move the bottleneck, they don't remove it. Here's what actually limits throughput in .NET systems.
A practical guide to designing long-running business processes with the Saga pattern - covering orchestration vs choreography, compensating transactions, timeouts, and observability.
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.
Idempotency at rest is easy. Two retries arriving at the same moment is the case that breaks the version most teams wrote.
Rollback is a database primitive. Distributed systems don't have one, and treating compensation as if they did is how workflows quietly break.
Every outbox explanation assumes the broker is what breaks. Here is what actually happens when the database is the thing that goes away.
Hi! Welcome to my blog
.NET, messaging, and distributed systems - the trade-offs the docs leave out.
Form not loading? Subscribe here.