You can use a public domain name for TDMQ for CMQ, which can be obtained in API Request Address in the console. However, we recommend you use a private domain name, as the public domain name incurs fees and may have a higher latency.
Currently, both collaborators and sub-accounts can use TDMQ for CMQ, but you need to grant them the permissions of TDMQ for CMQ resources in CAM.
All operations of the HTTP SDK are in sync mode, while you can choose async mode in the TCP SDK.
TDMQ for CMQ provides a visual console, so you can easily view the current queue status.
Go to the console >>
Both the message size and request size (for HTTP POST body) in TDMQ for CMQ can be up to 1 MB. When the message body is larger than 1 KB, we recommend the POST request method, as GET requests will be truncated and trigger exceptions.
If the message size exceeds 1 MB, you can solve it in the following two ways:
TDMQ for CMQ uses HTTP and TCP protocols, and its SDK maintains persistent TCP connections.
Currently, TDMQ for CMQ does not deduplicate messages. You can refer to Message Deduplication for the cause of duplicate messages and the deduplication scheme.
The queue has the
pollingWaitSeconds attribute, which indicates the default long polling time for the queue.
If a message is in the queue at the moment of message consumption, the system will return it immediately; otherwise, the system will wait for the time period specified by the
pollingWaitSeconds parameter. If there is a message during this period, the system will return it. However, if there is still no message after this period, the system will report a no message error.
You can set the
pollingWaitSeconds attribute of the queue as needed during message consumption instead of using the default value each time a message is consumed.