More complex to manage

Each microservice communicates via events with the others, the choreography-based approach can be more complex to manage and may require more coordination among the microservices.

▪ SAGA workflow become confusing when adding new steps into flow.

▪ Cyclic Event Consume Risk

There's a Cyclic Event Consume Risk dependency between saga participants because they have to

consume each other's commands.

▪ Result

Implementing the SAGA pattern will depend on the specific needs and constraints of the distributed system.

It may be a good fit for some systems, but may not be suitable for others.

▪ Choreography-based implementation of SAGA is good for simple workflows if they don't require too much micorservices transaction steps.

https://www.linkedin.com/pulse/microservices-saga-pattern-orchestration-vs-megha-gulati/