Apologies, I've confused the options rather. We'd thought about using
the dynamic federation features in M4 to get effective point-to-point
links between 'entry' nodes, and 'processing' nodes, in a distributed
app. The idea was that each app node would subscribe to a subset of
incoming messages (for load balancing), and the federation would take
care of getting the messages to the right place. Ideally there'd be no
message loss in the case of app node failover, ie, we want to maintain
the contents of an incoming work queue if the destination point of a
dynamically federated queue changed. I'd thought perhaps the atomic
rebinding feature could be useful here.
All that above sounded good, but I wasn't totally sure that it was
exactly how a dynamic federation behaved. Thinking about it a little
more, we realised that durable topic subscriptions would provide
similar functionality, with the benefit of a simplified setup that we
have more experience with.
The only slight downside is the additional latency in a centralised
clustered broker (as Carl mentioned). However, .35ms doesn't sound
that bad :)
Cheers,
Andrew
On 30 Jan 2009, at 21:14, Robert Greig wrote:
2009/1/29 Andrew Wright <[email protected]>:
There is currently debate going on as to the relative merits of a
centralised, active-active qpid cluster vs. local brokers on active-
active
application nodes. Given we're looking at using durable topic
subscribers,
does anyone have recommendations/suggestions/war stories about the
relative
broker setups?
I'm trying to understand the second option you describe. Are you
referring to what might be described as the "traditional" IBM MQ
topology where there is a local broker that federates into a central
remote broker?
RG
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
