← Path
Microservices Architecture · Microservices Data Consistency: Sagas, Outbox and Observability
0 XP- 1 current stop: learning
- 2 upcoming
- 3 upcoming
- 4 upcoming
- 5 upcoming
Finish after stop 5
Stop 1 of 5 · Furniture warehouse, step three failed
Trick to keep in mind+3 XP
A saga keeps an undo stack: completed steps are compensated newest first.
No single transaction spans separate databases, so each step commits locally and carries a business-level undo, such as a refund or releasing stock. When a later step fails, the compensations for finished steps run in reverse order. A compensation is a new action, not a database rollback, and some effects cannot be fully undone.
Read it once, then a question tests whether the trick stuck.