Day 9 of #DistributedDilemmas: Distributed transactions are a myth at scale
Distributed transactions are a myth at scale. Two-phase commit falls apart under network partitions. Design for compensation, not for distributed…
Two-phase commit falls apart under network partitions. Design for compensation, not for distributed atomicity.
2PC’s (2 Phase Commit) Fundamental Limitations:
When coordinator-participant communication fails after prepare phase, 2PC enters indefinite blocking where participants can’t safely commit/abort without coordinator. This creates the “cask effect” where one failure paralyzes the whole system. https://cs.stackexchange.com/questions/76192/why-is-two-phase-commit-2pc-blocking
Alibaba__Cloud ‘s distributed transaction solution uses Saga(Compensation Pattern) to handle cross-service payments:
- Order service creates order record
- Payment service deducts funds
- Notification service sends receipt
If any step fails:
- Payment Service → Reverse deduction
- Order Service → Mark order failed
- Notification → Cancel pending emails
https://www.alibabacloud.com/blog/an-in-depth-analysis-of-distributed-transaction-solutions_597232

Keep reading
🚀 Launching today: 28 Days of #DistributedDilemmas
Follow me on Twitter/X this February for one battle-tested insight a day on the hidden complexities behind outages, tech debt and architectural nightmares.
#DistributedDilemmas: all 24 days in one place
In February 2025 I posted one distributed systems dilemma a day on X. I made it to day 24. Here they all are, with the diagrams.
Cell-based architecture, explained: the public version of my Innovation Day talk
My Innovation Day deck was internal, so here's the public version: what a cell is, scaling up and across, blast radius, and what cells cost you.
Leave a comment