Using AMQP (RabbitMQ) for High Availablity in my applications -


I am putting a queue-based distributed system together, for all the standard stuff we provide to our messaging transport level, RabbitMQ Using the latest version of

I have a few questions about getting high availability (not for my applications but for rabbit MQs), which I could not read by reading the documentation. I appreciate some advice, this is probably the lack of understanding of the rabbit / AMQP which is causing the problem :)

Problem: I have a message maker (called Primary). One and only 1 message maker is

How can I get it using the current RabbleMQ capabilities?

Consideration: A "unique" queue, for which the primary will connect to the backup will try to connect this line of backups when the primary fails, the connectivity will be acquired in the backup queue and install the control on this process Can do.

What should I do to correct this? I did not find any documents on competitive producer, your advice would be appreciated!

If you want only one productive at a time - you do not tolerate it with the rabbit MQ mechanism (Unless you get some plug-ins, but I do not have any such information). You can gain control over the number of producers at the application level.

PS:

It seems that you are not getting proper AMQP consideration, manufacturers publish messages to the exchange, while consumers get them from the queue. Broker (rabbit MQ) route messages from the exchange or more (in fact, this is but this is another story).


Comments

Popular posts from this blog

ios - How do I use CFArrayRef in Swift? -

eclipse plugin - Run java code error: Workspace is closed -

c - Error on building source code in VC 6 -