[rabbitmq-discuss] Many queues, is there any practical limitation?

[Jerry Kuch]

Chapter 11 of the Manning book "RabbitMQ in Action" contains some very good
coverage of the actual resource costs of various Rabbit/AMQP constructs in
a running broker.  Having it on hand for reference and for supporting back
of the envelope calculations and estimates is likely to be very helpful.

Best regards,
Jerry

On Wed, Jul 24, 2013 at 5:21 AM, dniasoff <dniasoff at gmail.com> wrote:

> Hi,
>
> We are deploying a .Net application to many home users on regular internet
> connections.
>
> We might eventually reach an install base on 10'000s.
>
> The goal is to be able to "push" instant messages individually to any of
> these computers using RabbitMQ.
>
> As I am a RabbitMQ newbie, before trying various different scenarios to
> work out which will work best, I thought it's best to ask the "experts".
>
> A simple architecture would be a create an individual queue per client and
> have the client subscribe to it.
>
> Just wondering if this is the best approach or is there a neater approach
> as I guess having too many queues will consume server memory and be an
> overhead to maintain?
>
> I guess I should be asking  whether RabbitMQ the right tool for what I am
> trying to achieve and is it designed for this sort of scenario?
>
> Any pointers would be greatly appreciated :)
>
> Thanks
>
> Daniel
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130724/fc1c8751/attachment.htm>