In addition to retaining the characteristics of low latency, high performance, reliability, and scalability, and the capacity to process trillions of messages of its preceding versions, TDMQ for RocketMQ 5.x takes full advantage of the infrastructure and ecological technologies in the cloud native era to enhance resource usage and elasticity.
The 5.x series possesses the following strengths compared to self-built RocketMQ and the TDMQ for RocketMQ 4.x series:
Elastic Storage and Computing
The 5.x series of TDMQ for RocketMQ uses an architecture featuring separation of storage and computation, significantly enhancing both resource usage and elasticity. The storage operates on a pay-as-you-go basis. Customers do not need to reserve storage resources in advance for their peak demands, thereby effectively reducing the actual cost. It also supports elastic TPS for computing specifications, eliminating the need for customers to reserve additional computing resources for unexpected peaks, achieving higher cost efficiency.
Lightweight SDK
TDMQ for RocketMQ 5.x series is compatible with the open-source community SDK, thereby enjoying the benefits of iterative development. The client for the 5.x series is more lightweight, with a new minimalist API design that is easier to integrate and use. Moreover, the 5.x series offers SDKs in a greater variety of programming languages, providing developers with a wider range of technical stack options.
Enhanced Basic Features
The 5.x series of TDMQ for RocketMQ introduces several functional enhancements, such as more flexible control over the duration for which messages are retained, enabling the retention period to be set at the granularities of the cluster or the individual topic. Consumer groups also have more customizable settings. For example, the number of retry attempts for messages can be specified on the server side, and dead letter queues can be freely associated.
##Observability
The 5.x series of TDMQ for RocketMQ introduces a richer set of metrics, including those related to message backlog scenarios, key interface time consumption, error distribution, and storage read-write traffic. These metrics are integrated seamlessly with Tencent Cloud's monitoring and alarm services. Moreover, it provides a comprehensive cloud API that supports integration with self-service Ops systems.
Was this page helpful?