The Architecture of the Saga Pattern

We've discussed what the Saga Pattern is and why it's essential in distributed systems. We've also seen how the pattern works in general. Now we look at the architecture behind the pattern. The saga is what keeps data consistent across services once a single database transaction is no longer possible. Here is how it does that.

Local Transactions

A saga is composed of multiple local transactions. Each of these transactions is executed within a single service and its corresponding database. These local transactions are the building blocks of the saga