Microservices architecture and data consistency
summary
Microservices split data into per-service databases, so ACID or XA/2PC distributed transactions aren’t viable. The talk explains two concrete approaches to maintain data consistency across services—SAGA and LRA (Long Running Actions)—and demonstrates them using MicroProfile and the Eventuate Tram framework to help choose the right option for a microservices project.
AI-written summary · about
chapters (7)
- 0:00Microservices basics
- 5:39Distributed transaction issues
- 12:57MicroProfile LRA and Eventuate
- 15:24MicroProfile LRA demo
- 27:51Eventuate saga demo
- 38:18Solution comparison
- 40:24Conclusion
related talks
47mMicroservices Architecture and Data Consistency: So How Do We Do It for Real?
54mTackling transactions in a Microservices application
27mData Consistency in Microservices Architecture
55mTackling transactions in Microservices applications
51mPatterns & Practices of Implementing Event-driven MicroSvc...
41mTransactions in Your Micro-Services Architecture
39mManaging Consistency, State and Identity in Distributed Microservices
50mTransactional solutions for microservices