The Saga Pattern for Distributed Transactions
Learn to coordinate data changes across multiple services without distributed transactions using the saga pattern and compensating actions.
The Distributed Data Problem
In event-driven systems each service owns its own data. A single business operation may span several services, but there is no shared transaction to roll them all back.
What is a Saga?
A saga breaks one big transaction into a sequence of local transactions. If a step fails, earlier steps are undone with compensating actions.
All lessons in this course
- Building Event-Driven Microservices
- Integrating with Amazon EventBridge
- Real-time Processing with Kinesis
- The Saga Pattern for Distributed Transactions