Producers can create Topic to publish multiple types of messages, and consumers can subscribe to Topic for consumption on demand.
The users can view message status and content through TopicID and MessageID.
Messages that cannot be successfully delivered due to various reasons are placed on the Dead Letter Queue which can be viewed and delivered for consumption again.
Reset the message consumption progress within the time of persistent storage (3 days by default).
Solve asynchronous decoupling between businesses, peaking and filling of traffic, message communication, etc.
Sequential consumption (FIFO) shall be performed in the release order of messages.
The delivery is performed at a specified delay time point after the message-sending time (current time), for example, the delivery is performed 5 minutes after the sending time of the specified message.
Support Restful API, easy and convenient to access.
Provide SDK access of a more professional, reliable and stable SDK protocol.
Support elastic expansion which can increase or decrease resources as needed according to service conditions, to improve resource utilization rate and reduce the cost of consumption.
Provide a web console, API access interface and java SDK, easy to develop. It is also convenient for service support and service migration.
Provide features such as multi-dimensional monitoring for the running status and performance of resources, stability maintenance and so on. It also provides early warning notification to reduce daily maintenance workload.
Instances run in Virtual Private Cloud, enhancing security and isolation. Provide access restrictions such as subnets and IAM policies to protect against network attacks and safeguard your service privacy.
In the complicated multi-business system of an enterprise, many business processes don’t strongly depend on the core process, and can be placed in the JCQ for JCQ consumers to consume by need, without influencing the core primary process. such as e-commerce scenario (namely such systems as order, shopping cart, logistics and points).
In case of a difference between the upstream and downstream system processing capacity, JCQ will be used as the data buffer to control the information traffic. Consumption will proceed when the downstream system is capable of processing, so as to avoid invalid request and no service capacity. such as sec-killing, panic buying and other scenarios.
The producer has no need to care about the downstream consumer who subscribes the message. The many-to-many broadcasting mode is adopted, and consumption messages may be sent and received simultaneously. For example, message bus and configuration center update.
Receivers may response requests sent by the upstream system after a long time and may not be able to receive such requests because of network, outage, overload and other reasons, while the synchronous writing and three-copy backup of message queue can store the requests to guarantee asynchronous and reliable transmission of messages and timeliness and reliability of requests.
Scan, feedback the current page