Introducing Saga Pattern in Microservices with Spring Statemachine
summary
Explains how the Saga pattern implements multi-step transactions by composing local AC/D transactions plus compensating actions, using an event-driven stack and Spring Statemachine for state topology and orchestration. Shows an orchestration-based coordinator driving a fundraiser demo that accepts pledges, accumulates totals, marks matched campaigns, and runs compensating undo steps on failure; the demo code exists and the approach trades isolation for scalability while avoiding two‑phase commit.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:05What are sagas and state machines
- 8:30Monolithic vs distributed systems
- 13:52Challenges of distributed systems
- 26:23Consistency models explained
- 31:21Distributed transactions overview
- 36:44Introducing the saga pattern
- 41:24Saga compensating actions
- 44:31Handling saga isolation issues
- 47:41State machines in sagas
- 49:50Demo and conclusion
related talks
17mSaga Pattern for Distributed Transactions
27mBuilding Microservices Architecture The Right Way based on Saga Pattern
55mTackling transactions in Microservices applications
47mSaga Pattern Made Easy
50mTransactional solutions for microservices
01h 01mLost in transaction Strategies to manage consistency in distributed systems
41mTransactions in Your Micro-Services Architecture
46mLost in transaction? Strategies to deal with (in-)consistency in distributed systems