TDMQ for RocketMQ supports using multi-language client SDKs to send and receive messages over the TCP and HTTP protocols. This document describes the operation process of sending and receiving general messages over these two protocols.
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. If multiple consumers use the same group to consume messages, with some using the TCP protocol and others using the HTTP protocol, this may result in consumption failure and message repetition or loss.
Both the TCP and HTTP protocols support the public network and VPC access addresses, and VPC is used in the production environment by default. Public network access is not enabled by default. If you are using a virtual cluster, you can submit a ticket for application to enable it. If you are using a exclusive cluster, you can adjust public network bandwidthto enable or disable it. We recommend that you use public network access only in scenarios such as testing and debugging 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.
Yes
No
Was this page helpful?