Addressing the transaction challenge in a cloud-native world
summary
Challenges the assumption that cloud-native services must be stateless and claims stateful transactions are viable using Saga-style patterns; demonstrates an orchestrated implementation with a Narayana-based coordinator in open Liberty, coordinating a holiday-booking example (flight, hotel, taxi) and using MicroProfile’s MicroProfile LRA spec. Code shows annotations like @LRA @Complete @Compensate to join transactions and define compensating actions, explains tradeoffs versus 2PC (speed, locks, network failure) and points to a working GitHub demo and docs for reproduction.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:47Cloud-native applications matter
- 2:11Stateless vs stateful microservices
- 6:26Traditional ACID transactions
- 8:54ACID in microservices problems
- 12:45Saga pattern alternative
- 18:23MicroProfile LRA transactions
- 27:12Summary
- 29:17Q&A
related talks
46mAddressing the transaction challenge in a cloud-native world
50mTransactional solutions for microservices
53mA different flavor of the distributed transaction
51mExploring Stateful Microservices in the Cloud Native World
51mExploring Stateful Microservices in the Cloud Native World
54mExploring Stateful Microservices in the Cloud Native World
41mTransactions in Your Micro-Services Architecture
30mData Consistency Patterns in Cloud Native Applications