Concept notes
Why this decision matters
Saga Compensation Orchestrator is focused practice for Saga workflows and compensating actions. It explains why each answer is safe, risky, or production-ready.
Guide a distributed workflow through failure without losing its operational truth.
Backend concept notes
A Saga coordinates local transactions without pretending they form one global ACID transaction.
Compensation can fail and some effects cannot be reversed.
Common mistakes
- Keeping orchestration state only in memory.
- Calling compensation a rollback.
- Sending irreversible notifications before the pivot.
Review misses from this game
Related Backend Study Lab articles
Use the main site for deeper reading after playing.
Start here
Read deeper
Related Backend Study Lab tools
Use tools from the main site when you want to inspect real inputs.
FAQ
Short answers for how this game fits backend interview and study practice.
Does compensation restore the past exactly?
No. It is a new business action with its own rules and failure modes.
When is manual intervention appropriate?
When automated compensation cannot safely restore a truthful business state.