CMQ currently allows SDK calls based on the TCP protocol for sending and receiving general messages, transaction messages, delayed messages, and async messages. Among them, transaction messages can only be implemented through TCP.
The TCP protocol currently supports public network access and private network access from a CVM instance in a VPC in the same region as the CMQ instance, but does not support the private network access over the classic network.
This document describes how to use the SDK for TCP and install, download, configure, and run the demo to help you quickly build CMQ test projects.
TCP Protocol Advantages
Fewer computing resources
HTTP authenticates requests and requires a signature for each request, while TCP authenticates links; therefore, it is sufficient to authenticate a link during its establishment, which saves client computing resources.
Safer client threads
The TCP client is thread-safe, and multiple threads can use the same link, which saves link resources.
Higher transfer efficiency
TCP increases the proportion of valid data during transfer. For the same client, it has higher throughput and QPS and greater transfer efficiency than HTTP.
Better user experience
TCP supports async APIs and callbacks.
More features
TCP supports the latest CMQ feature of distributed message transaction.
Demo Usage
Preparing demo environment
1. Install IDE
You can install IntelliJ IDEA or Eclipse. This document uses IntelliJ IDEA as an example.
Please download IntelliJ IDEA Ultimate and install it accordingly.
2. Download the demo
Please download the CMQ demo to your local system and decompress it. You will see the cmq-java-tcp-sdk-master folder then.
Configuring demo
1. Create a resource
You need to create the required CMQ resource in the console and get the CMQ queue name, SecretID, and SecretKey.
