[dunhamda]

You can achieve seamless failover in RabbitMQ by running a clustered rabbitmq node on each of your clients, and configure the client to connect to its local rabbitmq. The cluster will take care of routing the messages to the active mirrored queue. (Note that on the consumer side your code must still properly handle consumer cancel notifications, but that's not too much to ask.)

This is architecturally similar to the mongodb/mongos solution described in the article.