TDMQ for RocketMQ is compatible with all components and principles of Apache RocketMQ, and supports connection to RocketMQ 4.6.1 or above without any modifications. It also has the underlying benefits of computing-storage separation and flexible scaling.
TDMQ for RocketMQ offers a multi-level resource structure that allows for both virtual isolation based on namespace and physical isolation at the cluster level. You may enable namespace-level permission verification to distinguish clients in different environments, which is simple and flexible.
As TDMQ for RocketMQ stores message data as shards, issues like data skew are rare. Rebalancing will not be triggered when nodes are added or deleted due to scaling or server fault, thus avoiding a significant reduction in cluster throughput.
TDMQ for RocketMQ supports multiple message types such as general, sequential, delayed, and distributed transaction messages. It also supports message retry and the dead letter mechanism, fully meeting the requirements in various business scenarios.
A single TDMQ for RocketMQ server can sustain a production/consumption throughput of up to 10,000 messages. With the distributed architecture and stateless services, the cluster can be scaled horizontally to increase the cluster throughput.
TDMQ for RocketMQ provides access APIs and open-source SDKs for all programming languages on all versions. It offers the entire set of OPS services of the Tencent Cloud platform and monitors alarms in real time to help you quickly discover and solve problems to guarantee the service availability.
The data of each transaction order needs to be monitored by dozens of downstream business systems, including item price approval, delivery, reward point, and stream computing analysis. Such systems use different message processing logic, making it impossible for a single system to adapt to all associated business. In this case, TDMQ for RocketMQ can implement efficient async communication and application decoupling to ensure the business continuity of the primary site.
Companies hold promotional campaigns such as new product launch and festival red packet grabbing from time to time, which often cause temporary traffic spikes and pose huge challenges to each backend application system. In this case, TDMQ for RocketMQ can act as a buffer to centrally collect the suddenly increased requests in the upstream, allowing downstream businesses to consume the request messages based on their actual processing capacities.
Sequential messages are used in some business scenarios, such as order creation, payment, delivery, and refund of in-app/game items, which are all strictly executed in sequence. Similar to the First In, First Out (FIFO) principle, TDMQ for RocketMQ offers a sequential message feature dedicated to such scenarios to ensure message FIFO.
Click "Contact Us" to enjoy personalized presales consultation and aftersales service.