This document describes the process and considerations for quickly using TDMQ for RocketMQ to implement regular message send and receive.
Notes
TDMQ for RocketMQ supports four types of messages: general, timed/delayed, sequential messages, and transactional. This document takes general message as an example. For other types of messages, refer to Message Type. Note:
Topics of different message types cannot be mixed, so the topics you create for general messages cannot be used to send and receive messages of other types.
TDMQ for RocketMQ supports accesses over the TCP and HTTP protocols. Therefore, we recommend that you create corresponding types of groups for these two protocols. This document introduces the TCP protocol as an example.
Notes:
If multiple consumers use the same Group to consume messages, and some use TCP protocol while others use HTTP protocol, it may lead to failed consumption, duplicate messages, or missing messages.
Both TCP protocol and HTTP protocol support public network and VPC network access addresses. The production environment recommends VPC network by default, and public network access is disabled by default. If you need to enable public network access, dedicated clusters can enable/disable it by adjusting public network bandwidth. Public network access is only recommended for testing or debugging scenarios that do not affect the production environment. Note:
The TCP and HTTP protocols can be supported in all regions. If the region where your current instance resides does not support the HTTP protocol and you need to use it, you can submit a ticket for application. Directions
The quick start operation process varies based on cluster type. The process for sending and receiving messages using TDMQ for RocketMQ is as shown below.