w.r.t to partitioning, I imagine a scheme where destinations 1-X exist on broker cluster A and X-N on broker cluster B. The client needs to randomly choose a destination or use some lookup/location mechanism. But as per Aaron's advice, do consider selectors as a way to reduce the destination count.
Also, be aware that there is a cost in dynamic network creation, all the advisories tend to slow things down if consumers come and go with any frequency. You may want to streamline routes though your network so that every node does not need to know about every destination. Filters will help here. Let us know how you get on. 2009/11/20 Igor Katkov <ikat...@gmail.com> > > Thank you, this is the kind of insight I was looking for. > > > Gary Tully wrote: > > > > It may be best to partition your destinations across a cluster. > > > > How do you mean it? > What I have in mind is a network of brokers, X producers generate messages > on one end of the network, Y consumers process them on the other end. > ActiveMQ takes care of storing messages in a different queues and > delivering > them to appropriate consumers. > > > -- > View this message in context: > http://old.nabble.com/500ooo%2B-queues--tp26417356p26438475.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
