Grokking Microservices Design Patterns
Vote

0% completed

​

The Saga Pattern: A Solution

We have seen the problem. The Saga Pattern is a design pattern for managing a transaction that spans several services.

What a Saga Is

In the simplest terms, a saga is a sequence of local transactions. A local transaction is an ordinary database transaction inside one service. Each local transaction updates that service's database and then triggers the next step of the saga. If a step fails, the saga runs a compensating transaction for every step that already committed. A compensating transaction is a new write that undoes the effect of one earlier step.

.....

.....

.....

Like the course? Get enrolled and start learning!
Prabhat Singh

Prabhat Singh

· 2 months ago

I am bit confuse about Real world analogy. How is it fulfilling the concept of Saga pattern? How are we going to call rollback and event publish by previous building? I feel, please provide more detailed explanation.

Show 1 reply

Reading Progress

0%


Vote for new content