Alibaba Cloud Message Queue for Apache RocketMQ has higher stability and security, and a better O&M system than an open source RocketMQ implementation. You can migrate open source RocketMQ clusters to Message Queue for Apache RocketMQ for better user experience. This topic describes the procedures for migrating open source RocketMQ clusters to Message Queue for Apache RocketMQ.

Principle

You must consume all messages in Message Queue clusters to be migrated. Producers and consumers send and receive messages in the RocketMQ clusters. The instances can be migrated one by one to minimize the impact on upper-layer services.

Benefits

Message Queue for Apache RocketMQ has the following benefits over open source RocketMQ implementations:
  • High stability: Message Queue for Apache RocketMQ is designated by Alibaba to provide the messaging service for the Double 11 Shopping Festival. Its availability and reliability have been tried and tested by the annual event over the past decade.
  • High performance: Message Queue for Apache RocketMQ provides messaging services for the annual Double 11 Shopping Festival, supporting the accumulation for hundreds of millions of messages with no impact on cluster services. The festival holds the global record for the largest volumes of concurrent messages (except log messages) and transactions (10 million transactions per second). Trillions of pieces of data are generated at 00:00 on the day of the festival.
  • Various message types: Message Queue for Apache RocketMQ provides different types of messages to meet the scenario-specific requirements of advanced features. Currently, supported message types include normal messages, ordered messages (globally ordered and partitionally ordered), distributed transactional messages, scheduled messages, and delayed messages.
  • Comprehensive O&M system: Message Queue for Apache RocketMQ supports the query of a message or the complete trace of a message, and message backtracking. These functions facilitate fast troubleshooting in the system and improve O&M efficiency.
  • RAM for security: Message Queue for Apache RocketMQ works together with Resource Access Management (RAM) to implement topic-level and subscription group-level access control on the receiving and sending requests of messages. Message Queue for Apache RocketMQ also supports Alibaba Cloud account with RAM users, blacklists and whitelists, Security Token Service (STS), Transport Layer Security (TLS), and access to Alibaba virtual private cloud (VPC).

Procedure

The following figure shows how to migrate an open source RocketMQ implementation to Message Queue for Apache RocketMQ:Migration flowchart

Step 1: Create a migration task

Create a migration task in the Message Queue for Apache RocketMQ console and import the metadata file exported from the open source RocketMQ implementation to Message Queue for Apache RocketMQ.

Step 2: Evaluate a migration task

Evaluate whether the technical and cost requirements are met for migration to the cloud.

Step 3: Migrate metadata

Migrate the metadata of topics and groups to a Message Queue for Apache RocketMQ instance in the cloud.

Step 4: Migrate the messaging service

Connect the nodes of message producer clusters and consumer clusters in batches to the Message Queue for Apache RocketMQ instance in the cloud. This way, message sending and receiving links can be migrated smoothly.