[rabbitmq-discuss] Architecture Question: 2 Brokers, or Not 2 Brokers ?
simone.busoli at gmail.com
Mon Jan 23 23:14:32 GMT 2012
On Mon, Jan 23, 2012 at 23:57, dnsplus <developer at dnsplus.net> wrote:
> Thank you for all this. If I were inclined to use central and remote
> exchanges/brokers, then SHOVEL is the missing piece I have been looking
> However ... oh, the overhead with maintaining it all !
Yes, I mentioned federation but in this context shovel is pretty much the
same thing, although perhaps a little lighter than federation. Going down
the route of several brokers, indeed, I see it becoming a pain quite soon.
> I suppose I am inclined to go with a Central Broker and have remote
> consumers, and was wondering if someone might convince me otherwise.
> However, this has not yet happened.
Perhaps some guys of the dev team can shed some light given their greater
> Seeing as how my application is more of a "task distribution and management
> system" where all sites are processing the same tasks (with RabbitMQ making
> sure that the tasks are received), it has occurred to me that I might want
> database component at the central data center as well. I am working on a
> conceptual workflow to flush this idea out.
I never used it personally, but if you're going to require a central store
anyway you may consider some messaging solutions that come with the storage
itself, after all according to what you describe you would be leveraging
just a very small part of what RabbitMQ provides. For instance MS SQL
Server ships with a built-in message broker, I don't know how it works but
it may be worth investigating, and I'm sure other storages provide that as
well. Some googling of "distributed work queues" may turn up something
> I keep coming back around to keeping as much intelligence as possible at
> Central, and keeping the consumer side as lean as I can.
> Thoughts ?
> View this message in context:
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss