tencent cloud

Migrating RabbitMQ to Cloud
Last updated: 2026-01-04 15:13:50
Migrating RabbitMQ to Cloud
Last updated: 2026-01-04 15:13:50

Migration Scenarios

RabbitMQ cluster migration mainly applies to the following two business scenarios:
1. Cross-environment migration: Migrate services from self-built or other cloud-based RabbitMQ clusters to TDMQ for RabbitMQ clusters.
2. Version upgrade migration: Migrate services from earlier RabbitMQ cluster versions (such as 3.8.30) to later versions (such as 3.13.7).

Recommended Solution: Dual-Write Dual-Consumption Migration

The solution is overall simple, clear, and easy to operate, with no data backlog, ensuring messages are consumed promptly, and business risks are controllable.

Migration Steps




Migration Step
Operation Description
Cluster Status
1.Migrate metadata.
1. Purchase a TDMQ for RabbitMQ cluster.
2. Complete metadata migration.
3. Keep the existing cluster in read-write status.
Existing cluster: Read-Write
New cluster: Ready
2.Enable dual-read.
1. Connect new consumers to the new cluster.
2. Keep parallel consumption on both the existing and new clusters.
Existing cluster: Read-Write
New cluster: Read-only
3.Enable dual-write and dual-read.
1. Connect new producers to the new cluster.
2. Gradually shift traffic to the new cluster through a grayscale release.
Existing cluster: Read-Write
New cluster: Read-Write
4.Enable single-write and dual-read.
1. Stop traffic to the producers of the existing cluster.
2. Keep the consumers of the existing clusters to continue processing residual messages.
Existing cluster: Read-only
New cluster: Read-Write
5.Complete the migration.
1. Confirm that all messages in the existing cluster have been consumed with no message backlog.
2. Take the existing consumer service offline.
Existing cluster: Offline
New cluster: Read-Write

Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback