Why is Two-Phase Commit (2PC) considered an anti-pattern in modern cloud microservices?
2PC requires a centralized coordinator to hold distributed lock leases across all participating databases simultaneously throughout a prepare and commit phase. If any network link falters or a participant stalls, database rows remain locked, exhausting connection pools and crippling system availability.
Answered in
Saga Pattern Demystified: Orchestration vs Choreography for Distributed Transactions and Compensating ActionsA comprehensive guide to the Saga pattern: Two-Phase Commit failure modes, compensating transactions, choreography vs orchestration, and idempotency.
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.