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.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.

What does a Saga do instead of trying to make multiple services' writes atomic together?

Next Step

Continue to What's the key difference between choreography-based and orchestration-based Sagas?← Back to all Spring Cloud questions