Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Message-ID: <6694831.1153818263276.JavaMail.jira@brutus>
Date: Tue, 25 Jul 2006 02:04:23 -0700 (PDT)
From: "james strachan (JIRA)" <jira@apache.org>
To: activemq-dev@geronimo.apache.org
Subject: [jira] Commented: (AMQ-816) new transport for load balancing client
 requests across many brokers
In-Reply-To: <31548809.1152635091486.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

    [ https://issues.apache.org/activemq/browse/AMQ-816?page=comments#action_36629 ] 
            
james strachan commented on AMQ-816:
------------------------------------

Was talking about this possible new feature with some users the other day and we tried to come up with a name to refer to this new kinda transport. I was previously struggling to think of one - then we ended up using the term 'jedi'. The name has kinda stuck - I think its cool :)

So we could call this the *jedi:* transport :)

> 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
>             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