Distributed Transactions: Why You Probably Do Not Need One
Two-phase commit, saga patterns, eventual consistency — most applications that reach for these could be redesigned to avoid the need.
DevDick / Field notes
Engineering decisions, research, setbacks and progress. A closer look at what changes—and what it means for people building software.
Two-phase commit, saga patterns, eventual consistency — most applications that reach for these could be redesigned to avoid the need.
Building a SaaS platform is not the same as building a web application with a subscription.
Running Kafka for 15,000 records per minute from 5,000 devices taught me things about stream processing that documentation does not cover.
The architecture that handles 10,000 active storefronts without falling over is not glamorous. It is disciplined.
They look similar. They are not. Choosing the wrong one creates problems that only appear at scale.
Both are excellent message brokers. The choice depends on your durability requirements, access patterns, and operational appetite.
Synchronous HTTP calls between services are simpler. Asynchronous messaging is more resilient. Here is when each is the right choice.
Nobody chooses microservices because they are a good starting point. On service decomposition done right.
Event-driven architecture solves real problems. It also introduces real complexity.
Read new published articles in your RSS reader. No account needed.
Good software starts with better questions.
Explore my work