RabbitMQ Migration with zero downtime

[Kamran Manzoor]

Hi All,

We have to migrate our RabbitMQ from one cluster to another and we would like to achieve this with zero downtime. We have read the green-blue migration strategy with queue federation as stated here:

https://www.rabbitmq.com/blue-green-upgrade.html 

However, we don't have clear a distinction between producers and consumers. For us, an application/service is both a producer and a consumer at the same time. 

We have read that the queue federation can be bi-directional. So we are thinking to apply bi-directional queue federation and start migrating our applications one by one to connect to the new RabbitMQ cluster. Do you think this migration approach is fine? I haven't found anyone using bidirectional queue federation for migration so thought of asking here. Looking forward to hear back from you. Many thanks in advance.

/Kamran

[Michael Klishin]

Queue federation is N-directional. Data is moved where the consumers are (with the preference for local consumers). That's what the blue/green deployment

strategy relies on. Most applications are not exclusively producers or consumers, this does not change anything if publisher-to-consumer locality in a cluster is not

mandatory in your system. E.g. request/reply with transient local queues may have to be migrated "all at once" with this approach.