@SzymonPobiega We are currently using Msmq and are transitioning to RabbitMq. We have a lot of services and there are various applications/processes that send commands to our services and/or subscribe to events published by our services. While my team owns the services, the applications/processes that consume our services are owned by other teams. I would like to implement a strategy that lets us update our service transport without affecting the consuming applications (so that they can transition at their own pace). We are currently using centralized FileBasedRouting to manage our message routing. I was considering to use NServiceBus.Router to bridge the transports. However, it looks like the sender needs to be aware of the router. Is there a way to implement the router/bridge that is agnostic to the sending application/process?
An alternate approach that I am considering is to have an intermediate/proxy service that forwards the messages to the router. So only the intermediate/proxy service will be aware of the router. We would configure the centralized message routing file to route all messages to the proxy service and the proxy service will in turn forward those messages to the actual destination endpoints through the router. I would appreciate your feedback about this approach or alternate suggestions.