{"id":1602,"date":"2022-07-04T13:14:22","date_gmt":"2022-07-04T07:44:22","guid":{"rendered":"https:\/\/ontoborn.com\/blog\/?p=1602"},"modified":"2022-07-12T23:50:06","modified_gmt":"2022-07-12T18:20:06","slug":"distributed-transaction-management-in-microservices-part-2-saga-pattern","status":"publish","type":"post","link":"https:\/\/ontoborn.com\/blog\/distributed-transaction-management-in-microservices-part-2-saga-pattern\/","title":{"rendered":"Distributed Transaction Management in Microservices \u2014 Part 2 \u2014 Saga Pattern"},"content":{"rendered":"\n
In this article, we are going to see about the Saga pattern which is an asynchronous pattern<\/strong> that performs a sequence of transactions in each microservice and publishes messages or events to proceed to the next step. If any step fails in between, compensating steps will be executed by the Saga pattern to reverse the transaction<\/p>\n\n\n\n