[rabbitmq-discuss] RabbitMQ-based vcloud session clustering

[Philippe Kirsanov]

That just a general question of server topology.
For running on cloud we should be able to throw in more machines (e.g.
using RightScale) and server farm should recognize that and use
additional resources to host more queues, maybe even exactly same queues
as exist on other brokers for the sake of scalability; end then
publishers and consumers should load balance those queues on different
brokers.

-----Original Message-----
From: Alexis Richardson [mailto:alexis.richardson at gmail.com] 
Sent: Wednesday, April 07, 2010 14:22
To: Philippe Kirsanov
Cc: Jon Brisbin; RabbitMQ
Subject: Re: [rabbitmq-discuss] RabbitMQ-based vcloud session clustering

Philippe

In what sense?  I imagine most folks would treat VMs as machines.  But
perhaps the VMware product suite could be helpful too....

alexis



On Tue, Apr 6, 2010 at 5:15 PM, Philippe Kirsanov
<pkirsanov at 38studios.com> wrote:
> Just curious, how do you do load balancing with VMware?
>
> -----Original Message-----
> From: rabbitmq-discuss-bounces at lists.rabbitmq.com
> [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Jon
> Brisbin
> Sent: Monday, April 05, 2010 17:53
> To: RabbitMQ
> Cc: Tomcat Users List
> Subject: [rabbitmq-discuss] RabbitMQ-based vcloud session clustering
>
> Not sure there's anyone besides me on both these lists, but I'm
> x-posting just to save time.
>
> I'm currently working on setting up a RabbitMQ-based session cluster
> using my own session manager and store. I had to write my own because
I
> couldn't find anything out there that uses JMS or RabbitMQ to do
session
> clustering (which actually surprised me a little) that had the virtual
> cloud awareness I need. Everything I've read about Tomcat clustering
> uses the Apache Tribes replication, which doesn't work for me under
even
> moderate load testing (maybe I'm just not doing right...I don't know)
or
> the centralized JDBCStore, which introduces a single point of failure.
>
> The basic idea here is to use RabbitMQ as the session clustering
> back-end and have a user's session available to any server currently
> subscribed to the clustering queue with no sticky sessions at all.
This
> (cross your fingers) gives me a very, very scalable clustering
> architecture (my RabbitMQ servers are load-balanced and clustered
using
> VMware vms so I can add capacity at will) that doesn't suffer from the
> single point of failure of a JDBCStore or the multicast limitations of
> Apache Tribes. Sessions are also shared across points of
responsibility,
> too, as a single session object can be passed around from code running
> inside a webapp to code in a command-line client. I wanted my session
> handling to be a first-class virtual cloud citizen, rather than feel
> like I'm shoe-horning existing code into what I want to do.
>
> I'm almost finished with the heavy lifting. I should have a
functioning
> drop-in manager and store this week, which I'll put on my github
> account. What I'd like to know is if there's any interest in the
> community for something like this? If there's no interest, I won't
> bother writing documentation and what-not.
>
> Does this sound like it would interest any other Tomcat/RabbitMQ
users?
>
> Jon Brisbin
> Portal Webmaster
> NPC International, Inc.
>
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>