[rabbitmq-discuss] what is the best way of implementing client-server arcitecture?

ivan.lysov ivan.lysov at gmail.com
Fri Jul 13 08:08:57 BST 2012

I'm wondering how the server should consume the messages. 
1. There is one queue where all the messages from all the clients are
 a) would it be a bottleneck especially when the size of messages is pretty
 b) is it the size that really matters in this case?
2. There are many queues, one for each client.
 a) would it be a performance issue to keep on listening all the queues?
 b) is it the number of clients that matter in this case?
3. There are several queues that server listens to, the messages are
delivered by some special algorithm (for example, grouped by categories or
 a) does it make sense at all? And if it does, what is the best practices
algorithm for such message distributing?

Sure, there is no big deal in trying all these cases in test projects (what
i'm going to do right now), measuring performance etc., but i'm also sure
that there is a best way of implementing this. So i need your help.

Thank you!

View this message in context: http://rabbitmq.1065348.n5.nabble.com/what-is-the-best-way-of-implementing-client-server-arcitecture-tp20768.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

More information about the rabbitmq-discuss mailing list