On Friday 03 June 2011 03:33:13 Robert Collins wrote: > Rabbit has an awkward high availability story; specifically its not > trivial to get the reliability we have out of HTTP services, This is > partly because rabbit clusters don't distribute the queues and because > its a more stateful and complex system than HTTP. Long story short we > won't be in a position to use queues for persistence and its simpler > to use HTTP to gracefully handle a single backend node dying.
This makes me sad :/ Queues are massively more useful if they are persistent and this is one aspect that I was really looking forward to working with. There's ways around it of course, but it makes things more awkward for the consumer. Presumably you've been looking at http://www.rabbitmq.com/pacemaker.html ? I've had a quick glance but not digested anything. Cheers. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
