On 09/24/2010 02:09 PM, David Hawthorne wrote:
I myself am more worried about the scaling aspect. How is that solved?
Federation might help you, it allows messages to be automatically routed between brokers which could be used to distribute load.
Partitioning your application is another thing to think about: i.e. separate the load into chunks that can be run on separate brokers.
If you need both scaling and reliability, think of a qpid cluster as a *single reliable broker* and then federate or partition over multiple clusters.
I'm very interested in discussion about how the reliability and scalability aspects could live more harmoniously together. I'm thinking about some reworking to make the cluster more flexible and I think there will be scope to address scalability+reliability with a more coherent solution, the cluster effort has been very reliability-focused till now, so it would do me good to think a bit more about the scalability aspect while I'm thinking about improved cluster design.
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
