Saga pattern: orchestration vs choreography in practice

We're facing a classic distributed transaction problem with a flow that spans about 5 different microservices for order fulfillment. We've been looking into the Saga pattern, and the debate is whether to go with orchestration or choreography. Orchestration seems appealing because you have a central 'saga orchestrator' service that dictates the sequence of operations and handles rollbacks. It's easier to understand the overall flow and debug if something goes wrong. The concern is it becomes a single point of failure and could potentially create a new monolith if not carefully designed. Choreography, on the other hand, relies on services publishing events and reacting to them, making it more decentralized and resilient. But then it's much harder to visualize the entire transaction path and debug when failures occur. It can also lead to event storms. What are people's real-world experiences with these? When do you choose orchestration over choreography, or vice-versa? Are there hybrid approaches that mitigate the downsides of each?