Ok,
If we really want to be loosely coupled one service/ESB component should not even know the other exists.
Im a little confused .. If 1 orchestration executes all the steps in the itinerary , then it would also need to know “how ” to execute all the steps.
So if the itinerary is altered for a message the same orchestration would need to understand the exact way to communicate with the newly introduced steps etc.
How is this dynamic if I need to add a new step to a few of the itineraries and also modify the corresponding orchestrations which are affected ?