Greetings, I am trying to test my service bus saga from my development machine, which wasn't a problem until I deployed the code to the server. I have the service bus queue name as a configuration variable, so messages of type "StartCreateUserSaga" when running on my local machine go to the "userservicelocal" queue and messages from the deployed server go to the "userservice" queue. However, the messages are going to both queues whether they are sent from the server to the "userservice" queue or from my local machine to the "userservicelocal" queue. Since both queues have different saga storage (local postgres vs. server postgres) this causes a mess, aside from the inability to guarantee that my local machine will process it so I can debug.
I am failing to see what the point is of having named queues if any queue in an Azure Service Bus instance will pick up messages of its configured type whether or not they actually are directed to the queue in question. Unless I'm really missing something fundamental the entire point of named queues is to direct traffic to its intended consumer.
We have separate Azure Service Bus instances in separate resource groups for our different deployed environments (dev, qa, uat, prod) but not for 'local' development. Creating an instance for 'local' use would be the obvious work around but I would like to understand why ASB is behaving in this very sub-ideal fashion.
Thanks in advance