You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2006/07/11 18:28:51 UTC

[jira] Commented: (AMQ-816) new transport for load balancing client requests across many brokers

    [ https://issues.apache.org/activemq/browse/AMQ-816?page=comments#action_36560 ] 

Hiram Chirino commented on AMQ-816:
-----------------------------------

Sounds similar to the fanout transport we currently have.  Except that in the fanout transport it's backwards.
We broadcast the publish to multiple brokers and only consume from 1.



> new transport for load balancing client requests across many brokers
> --------------------------------------------------------------------
>
>          Key: AMQ-816
>          URL: https://issues.apache.org/activemq/browse/AMQ-816
>      Project: ActiveMQ
>         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:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira