activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Commented: (AMQ-816) new transport for load balancing client requests across many brokers
Date Tue, 12 Sep 2006 06:13:23 GMT
    [ ] 
james strachan commented on AMQ-816:

We currently have the fanount transport which does most of this - the main thing to add is
the ability to choose the broker to send a command to depending on the context. e.g. when
using a transaction, choose a broker and use it for the entire transaction (unless the broker
dies). When sending a MessageAck use the broker that sent the original message etc.

> new transport for load balancing client requests across many brokers
> --------------------------------------------------------------------
>                 Key: AMQ-816
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>            Reporter: james strachan
>             Fix For: 4.2
> Rather than creating store and forward networks, it might be nice to have a kind of composite
transport where...
> * consumers are created on each broker found/discovered. This allows messages to be sent
to any broker and consumed by any consumer
> * producers could dynmically choose which broker to send a message to (or could just
pick one broker per session/producer)
> this allows for a load balancing layer at the client side which avoids the need for store/forward
networks (which results in more network traffic and often increases load on the brokers).
> So it basically pushes load back to the clients. The downside of this appoach is that
the clients have more connections to brokers - but given the linear scalability of this, it
sounds a great idea to me at least :)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message