[rabbitmq-discuss] Queues Per Client or Per Company
michael.s.klishin at gmail.com
Fri May 6 21:01:24 BST 2011
A common solution is to use one server-named exclusive queue per client and a well-known, durable queue for the server, then use message-id and reply-to message headers to identify peers and replies.
A few hundred queues is certainly something Rabbit can handle easily. In fact, queues number matters less than number of bindings and message copies that have to be delivered. In your case it sounds like one client request will result in one message being delivered to the server, and one server reply is routed to just one client. Not a big deal.
On venerdì 6 maggio 2011 at 23.27, Marcus Vinitius Baffa wrote:
> The Users, Client applications, will send commands to the server application that will execute it and return a response (typical async RPC). The server application will push to Users and to the Groups relevant informations.
More information about the rabbitmq-discuss