- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- Best Practices
- API Documentation
- SDK Documentation
- FAQs
- General References
- Service Level Agreement
- Contact Us
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- Best Practices
- API Documentation
- SDK Documentation
- FAQs
- General References
- Service Level Agreement
- Contact Us
Overview
This document describes the schemes for migrating a self-built RabbitMQ cluster to a TDMQ for RabbitMQ cluster. You can choose an appropriate scheme according to your own business scenarios.
Scheme Description
Scheme 1. Single-producer single-consumer (recommended)
This scheme is simple, clear, and easy to implement. It also ensures the sequence of messages.
Directions:
1. Purchase a TDMQ for RabbitMQ cluster.
2. Migrate the RabbitMQ metadata.
3. Switch all producers to the TDMQ for RabbitMQ cluster.
4. After all the data in the self-built cluster is consumed, stop the consumption service.
5. Change the RabbitMQ listening address of the consumer service to the TDMQ for RabbitMQ address and start the service.
Pros and cons of the scheme:
Pros: he overall migration process is simple, clear, and easy to implement for smooth transition. It guarantees message consumption in sequence, saves costs, and avoids the need to start new consumers.
Cons: When producers are switched to the TDMQ cluster, if there are too many messages heaped in the self-built cluster, messages cannot be consumed in time in the TDMQ cluster, which may cause consumption delays.
Scheme 2. Single-producer dual-consumer
This scheme is simple, clear, and easy to implement, with no data heap. It can ensure the prompt consumption of messages but cannot ensure the sequence of messages.
Directions:
1. Purchase a TDMQ for RabbitMQ cluster.
2. Migrate the RabbitMQ metadata.
3. Switch all producers to the TDMQ for RabbitMQ cluster.
4. Start a new RabbitMQ consumer to consume messages in the TDMQ for RabbitMQ cluster.
5. After all the data in the self-built cluster is consumed, disable the consumption service in the self-built cluster.
Pros and cons of the scheme:
Pros: This scheme is simple, clear, and easy to implement, with no data heap. It can ensure the prompt consumption of data.
Cons: After the producer is switched and the new consumer is started, if there are messages heaped in the self-built cluster, disordered messages may appear. In addition, the cost is higher since a new consumer needs to be started.
Yes
No
Was this page helpful?