Saga pattern: orchestration vs choreography in practice

we're dealing with distributed transactions across about 5 different microservices for a core e-commerce workflow, and the saga pattern keeps coming up. the debate is whether to go with orchestration or choreography. orchestration, where a central saga coordinator manages the steps, feels easier to reason about and debug. you can clearly see the state transitions. but then that coordinator becomes a single point of failure and potentially a bottleneck. choreography, where services react to events from other services, is more decentralized and resilient, but debugging a failed transaction across multiple event streams feels like a nightmare. what are the practical trade-offs people have experienced when choosing between these two? has anyone found a good middle ground, perhaps an orchestrator that's itself distributed?