I was going through https://docs.microsoft.com/en-us/azure/architecture/patterns/choreography, the document mentions in the drawbacks of having a central orchestrator that it can become a performance bottleneck. This is something I didn't get, because even if we move towards the choreography pattern as described, any workflow will still have to pass through each and every service involved. I don't see how it can be a bottleneck unless it was making a parallelizable workflow sequential.
I understand the benefits of this, like reduced coupling and the ease of bringing in new components into the flow, but could not get the performance bottleneck part. Can someone please explain what I'm missing here ?