You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2008/09/08 16:55:58 UTC

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

     [ https://issues.apache.org/activemq/browse/AMQ-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-816:
---------------------------

    Fix Version/s: 5.3.0
                       (was: 5.2.0)

> new transport for load balancing client requests across many brokers
> --------------------------------------------------------------------
>
>                 Key: AMQ-816
>                 URL: https://issues.apache.org/activemq/browse/AMQ-816
>             Project: ActiveMQ
>          Issue Type: Improvement
>            Reporter: James Strachan
>            Assignee: Rob Davies
>             Fix For: 5.3.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.