How do microservices handle cross-service transactions without two-phase commit?
Through the Saga Pattern paired with the Transactional Outbox pattern. A saga coordinates multi-step business transactions as a series of local database commits linked by asynchronous events, using compensating transactions to roll back state if a step fails.
Answered in
Microservices Architecture: Bounded Contexts, Event-Driven Decoupling and Database SplittingArchitectural guide to splitting monoliths: defining bounded contexts, managing distributed transactions with Sagas, and avoiding microservice sprawl.
Read the full analysisOther questions this article answers
More system design & architecture questions
- What is the architectural difference between an API Gateway and a Reverse Proxy?
- When should an architecture use Layer 4 instead of Layer 7 load balancing?
- How do edge ingress layers prevent backend cascading thundering herds?
- What algorithm is best for sticky sessions without breaking even distribution?
- How can a CDN improve performance for dynamic requests?
- What is the hardest part of operating behind a CDN?
- How can a CDN help with traffic surges or DDoS attacks?
- What is the difference between a Push CDN and a Pull CDN?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.