Tackling transactions in a Microservices application
summary
Explains the loss of ACID transactions when moving from monolithic apps to distributed microservices, discusses CAP trade-offs and alternatives for ensuring cross-service data consistency, and presents the SAGA pattern as a practical approach to implement distributed transactions.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:05Commit Request Phase
- 6:27Commit Phase
- 8:152 Phase Commit Pros
- 9:162 Phase Commit Cons
- 12:59Sagas vs 2PC
- 33:45SEC Failure
- 35:18Higher Cohesion & Composable Services
- 36:26Isolation of Complex Code
related talks
55mTackling transactions in Microservices applications
46mMicroservices architecture and data consistency
41mTransactions in Your Micro-Services Architecture
51mPatterns & Practices of Implementing Event-driven MicroSvc...
28mPractical Approaches To Scaling Distributed Transactions
17mSaga Pattern for Distributed Transactions
50mDeveloping Microservices with Aggregates
27mData Consistency in Microservices Architecture