Saga Orchestration Pattern (Managing Distributed Transaction in ASP.NET Core Microservices)

In this video, I will walk through implementing the Saga Orchestration pattern for managing distributed transactions in ASP.NET Core microservices. Managing transaction across multiple microservices is a hard problem to solve. The saga pattern was introduced to solves this problem of managing the distributed transactions. For the orchestration pattern, as the name suggests in the orchestration implementation there is a centralized orchestrator. The orchestrator tells each microservice which operation to perform. And in case of issues, it also sends messages to different microservices for a rollback of transactions. It manages the state of each task through a state machine. Pros: 1. Highly scalable logic since individual microservices do not have to talk to each other. 2. No possibility of cyclic dependency between microservices. In videos where I have discussed the basic concepts of Saga design pattern here: Saga Pattern: https://youtu.be/Z4Ug7NL2VAk Saga Choreography Pattern: https://youtu.be/Mau9hxONzZ8