Benefits

▪ Provides a clear and centralized point of control for managing transactions.

▪ Make it easier to understand and debug the system, and to add new transactions or modify existing ones.

Drawbacks

▪ The orchestrator can also become a single point of failure, and if it goes down, the entire system may be unable to complete transactions.

▪ The orchestrator can become a bottleneck if the system is heavily loaded, as all transactions must go through it.

Result

▪ It can be a useful approach for managing transactions in a distributed system, but it is important to carefully consider the trade-offs and potential drawbacks.

▪ Orchestration way is good for complex workflows which includes lots of steps.

▪ But this makes single point-of-failure with centralized controller microservices and need implementation of complex steps.

https://medium.com/swlh/microservices-architecture-what-is-saga-pattern-and-how-important-is-it-55f56cfedd6b