[rabbitmq-discuss] Creating exchanges on demand.

Alexis Richardson alexis.richardson at gmail.com
Fri Jun 5 20:57:04 BST 2009

Almost certainly.  Try to reuse the routing layer (exchanges) as much
as possible.

On Fri, Jun 5, 2009 at 8:56 PM, Camilo Lopez<camilol at gmail.com> wrote:
> Thanks for the advice,
> I just changed my code to have many different bindings to a couple of
> exchanges it works the same, and I think is a much  better way of
> doing things.. right?.
> On Fri, Jun 5, 2009 at 3:53 PM, Alexis Richardson
> <alexis.richardson at gmail.com> wrote:
>> As Matthias implies, having as many exchanges or queues as you have
>> messages... is an ANTIPATTERN.  Avoid!
>> On Fri, Jun 5, 2009 at 8:48 PM, Matthias Radestock<matthias at lshift.net> wrote:
>>> Camilo,
>>> Camilo Lopez wrote:
>>>> OK, I am mostly worried about the possible performance/memory hit, I
>>>> don't want to put some code in production and realize I just run out
>>>> of memory or becoming unresponsive. So I undestand that's not the
>>>> case.
>>> Creating a new exchange, or queue, or binding for every message would
>>> definitely be a bad idea. As suggested already, check out the rpc
>>> convenience wrappers in the various client libs.
>>> Matthias.
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list