advancedThe Saga Pattern
What does a Saga do instead of trying to make multiple services' writes atomic together?
It breaks a business operation into a sequence of independent LOCAL transactions, each fully committing on its own, with an explicit compensating transaction defined for each step to undo it if a later step in the sequence fails.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response