[rabbitmq-discuss] Custom Exchange Implementation

Martin Sustrik sustrik at imatix.com
Wed Mar 25 16:07:12 GMT 2009

Nice. One idea though:

When no node is assigned to a freshly arrived routing key, choose the 
one that has least routing keys attached. If there are several with 
lowest number of bindings choose the first one.

That would spread the load more evenly.


Levi Greenspan wrote:
> On Wed, 2009-03-25 at 15:33 +0000, Alexis Richardson wrote:
>> Levi
>> That's fascinating.  Can I ask what application you have that requires this?
>> alexis
> Sure. What I have is a frontend and a backend  with RabbitMQ in between.
> The frontend and the backend consist of multiple nodes to spread the
> load. However I need to consistently route the traffic from the frontend
> to the same node in the backend. Initially the routing key is only known
> in the frontend, so I can not have backend nodes binding themselves to
> the exchange, as they don't know the key. Hence my custom exchange type,
> that binds the queues dynamically.
> Cheers,
> Levi
> _______________________________________________
> 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