Hi,
I have a question around the design / usage of Queues.
We have a need for many client instances (sitting across business borders) to send data to a server instance and we're looking at Azure Service Bus / Message Queues to wire the clients-server together. One analogy of this architecture would be of an order system where many clients are sending their orders in, and the server responds with order status updates.
Using a single queue to send/receive the data for the server appears straight forward, however my scalability query resolves around how the server queues notification messages back to a specific client in a secure manner. Would we need to create a queue per client to guarantee messages for one client are not picked up by another, or is there another "single-queue" scalable mechanism we could rely on (similar to a conversation)?
Thanks,
Jay :)
If you shake a kettle, does it boil faster?