Selection Recommendations

Last updated:2026-01-23 17:09:49

Selection Recommendations

Last updated: 2026-01-23 17:09:49

Selection Overview
Before purchasing a TDMQ for RocketMQ instance, you need to comprehensively consider key factors such as business scenarios, usage scale, and pricing to select the most suitable instance specifications. Different types of TDMQ for RocketMQ instances vary in specifications, performance capabilities, and resource calculation logic. This document details the specification characteristics and calculation methods of each edition to help you make a quick selection.
Product Form Selection
Product Forms
TDMQ for RocketMQ provides two mainstream versions, 4.x and 5.x, for customers to choose from, meeting diverse needs across different business scenarios, usage scales, and price points.
For more information about product forms and detailed feature differences, see Feature Comparison.
Product Form Selection Recommendations
For different versions and product forms, you can make selections based on applicable scenarios, specification ranges, and differentiated features:
Recommended Cluster Type
﻿
Applicable Scenario
Specification Range
Differentiated Feature
4.x series
4.x exclusive cluster
With large-scale business operations and high usage volumes.
Require physical isolation between components and demands high availability.
Fine-grained Ops: Require transparency and monitoring capabilities for each node.
High business flexibility: Support business isolation and division across multiple departments.
TPS range: 4,000 to 360,000
Number of free topics: 500 to 8,000
Number of free groups: 5,000 to 80,000
Transparently display the number of broker nodes and show the distributed queue information for each broker.
Support creating up to 10 namespaces under a single cluster for inter-business isolation.
Support fine-grained permission control for the data plane at the namespace level.
﻿
4.x general cluster
With large-scale business operations and high usage volumes.
Require physical isolation between components and demands high availability.
Fine-grained permission management for the data plane.
Cost-effective solution balancing performance and budget.
TPS range: 8,000 to 80,000
Number of free topics: 400 to 4,000
Number of free groups: 4,000 to 40,000
Support fine-grained permission control for the data plane at the topic and group levels.
5.x series
5.x Basic Edition
Test environments or low-volume usage scenarios.
The latest community 5.x SDK is used.
Benefit from more 5.x capabilities, such as richer monitoring metrics, pay-as-you-go storage, and server-side retry mechanisms.
Cost-effectiveness as a key consideration.
TPS range: 1,000 to 10,000
Number of free topics: 100 to 200
Number of free groups: 1,000 to 2,000
/
﻿
5.x Pro Edition
Production environments with moderate usage levels.
The latest community 5.x SDK is used.
Benefit from more 5.x capabilities, such as richer monitoring metrics, pay-as-you-go storage, and server-side retry mechanisms.
Cost-effectiveness as a key consideration.
TPS range: 4,000 to 100,000
Number of free topics: 300 to 1,000
Number of free groups: 3,000 to 10,000
Support fine-grained permission control for the data plane at the topic and group levels.
Support enabling instantaneous elastic TPS traffic
﻿
5.x Platinum Edition
Production environments with substantial usage demands
Require physical isolation between components and demands high availability
The latest community 5.x SDK is used.
Benefit from more 5.x capabilities, such as richer monitoring metrics, pay-as-you-go storage, and server-side retry mechanisms.
Cost-effectiveness as a key consideration.
TPS range: 10,000 to 100,000
Number of free topics: 1,000 to 10,000
Number of free groups: 10,000 to 100,000
Support fine-grained permission control for the data plane at the topic and group levels.
Support enabling instantaneous elastic TPS traffic
Note:
Current 4.x virtual clusters and 5.x trial clusters have been discontinued for new purchases. Existing clusters remain unaffected and will continue to receive upgrades and maintenance. It is recommended to upgrade or migrate to other cluster types at the earliest opportunity.
Specification Selection
After selecting a version, you can select appropriate specifications based on your business usage. The following table describes the key factors that influence specification selection:
Specification Selection Consideration Factor
Description
TPS
This includes the total number of produced and consumed messages, which is calculated based on the message size and message type. For more information, see Pricing for each edition.
Each cluster edition enforces strict traffic throttling on TPS specifications. Exceeding the cluster's TPS limit will trigger traffic throttling. When selecting TPS specifications, consider peak TPS impact and reserve a buffer for traffic fluctuations. For 5.x Pro Edition and Platinum Edition clusters, elastic TPS can be enabled to handle burst traffic peaks.
Storage
For 4.x exclusive clusters and general clusters, comprehensive consideration should be given to factors such as message write rate, message size, and message retention period. For example: If the average message size is 1 KB, average production TPS is 10,000, and messages are retained for 3 days (72 hours), the actual storage space required is: 1 KB x 10,000 x 3,600 x 72/1,000,000 GB = 2,592 GB. Based on cloud disk specifications, this can be rounded up to a minimum cluster storage capacity of 2,600 GB.
The entire 5.x cluster series incorporates technical optimizations within a storage-compute separation architecture. Storage is billed based on actual usage through post-payment settlement, eliminating the need for pre-purchased storage capacity. This significantly reduces your storage costs. For more information, see 5.x Cluster Billing Overview.
Number of topics
Different cluster editions offer varying numbers of free topics. If you need to purchase additional topic quotas, you can buy them on demand based on the actual exceeded quantity.
Cluster load
On the Cluster Details page and monitoring page, the cluster's TPS load is calculated based on the current TPS and the purchased TPS specification. The calculation formula is: Current TPS/Purchased TPS specification x 100%. If the cluster load is excessively high, it is recommended to upgrade the cluster specifications according to your actual scenarios.
﻿

Was this page helpful?

You can also Contact Sales or Submit a Ticket for help.

Yes

Feedback

Recommended Cluster Type			Applicable Scenario	Specification Range	Differentiated Feature
4.x series	4.x exclusive cluster	With large-scale business operations and high usage volumes. Require physical isolation between components and demands high availability. Fine-grained Ops: Require transparency and monitoring capabilities for each node. High business flexibility: Support business isolation and division across multiple departments.	TPS range: 4,000 to 360,000 Number of free topics: 500 to 8,000 Number of free groups: 5,000 to 80,000	Transparently display the number of broker nodes and show the distributed queue information for each broker. Support creating up to 10 namespaces under a single cluster for inter-business isolation. Support fine-grained permission control for the data plane at the namespace level.
4.x series		4.x general cluster	With large-scale business operations and high usage volumes. Require physical isolation between components and demands high availability. Fine-grained permission management for the data plane. Cost-effective solution balancing performance and budget.	TPS range: 8,000 to 80,000 Number of free topics: 400 to 4,000 Number of free groups: 4,000 to 40,000	Support fine-grained permission control for the data plane at the topic and group levels.
5.x series	5.x Basic Edition	Test environments or low-volume usage scenarios. The latest community 5.x SDK is used. Benefit from more 5.x capabilities, such as richer monitoring metrics, pay-as-you-go storage, and server-side retry mechanisms. Cost-effectiveness as a key consideration.	TPS range: 1,000 to 10,000 Number of free topics: 100 to 200 Number of free groups: 1,000 to 2,000	/
		5.x Pro Edition	Production environments with moderate usage levels. The latest community 5.x SDK is used. Benefit from more 5.x capabilities, such as richer monitoring metrics, pay-as-you-go storage, and server-side retry mechanisms. Cost-effectiveness as a key consideration.	TPS range: 4,000 to 100,000 Number of free topics: 300 to 1,000 Number of free groups: 3,000 to 10,000	Support fine-grained permission control for the data plane at the topic and group levels. Support enabling instantaneous elastic TPS traffic
		5.x Platinum Edition	Production environments with substantial usage demands Require physical isolation between components and demands high availability The latest community 5.x SDK is used. Benefit from more 5.x capabilities, such as richer monitoring metrics, pay-as-you-go storage, and server-side retry mechanisms. Cost-effectiveness as a key consideration.	TPS range: 10,000 to 100,000 Number of free topics: 1,000 to 10,000 Number of free groups: 10,000 to 100,000	Support fine-grained permission control for the data plane at the topic and group levels. Support enabling instantaneous elastic TPS traffic

Specification Selection Consideration Factor	Description
TPS	This includes the total number of produced and consumed messages, which is calculated based on the message size and message type. For more information, see Pricing for each edition. Each cluster edition enforces strict traffic throttling on TPS specifications. Exceeding the cluster's TPS limit will trigger traffic throttling. When selecting TPS specifications, consider peak TPS impact and reserve a buffer for traffic fluctuations. For 5.x Pro Edition and Platinum Edition clusters, elastic TPS can be enabled to handle burst traffic peaks.
Storage	For 4.x exclusive clusters and general clusters, comprehensive consideration should be given to factors such as message write rate, message size, and message retention period. For example: If the average message size is 1 KB, average production TPS is 10,000, and messages are retained for 3 days (72 hours), the actual storage space required is: 1 KB x 10,000 x 3,600 x 72/1,000,000 GB = 2,592 GB. Based on cloud disk specifications, this can be rounded up to a minimum cluster storage capacity of 2,600 GB. The entire 5.x cluster series incorporates technical optimizations within a storage-compute separation architecture. Storage is billed based on actual usage through post-payment settlement, eliminating the need for pre-purchased storage capacity. This significantly reduces your storage costs. For more information, see 5.x Cluster Billing Overview.
Number of topics	Different cluster editions offer varying numbers of free topics. If you need to purchase additional topic quotas, you can buy them on demand based on the actual exceeded quantity.
Cluster load	On the Cluster Details page and monitoring page, the cluster's TPS load is calculated based on the current TPS and the purchased TPS specification. The calculation formula is: Current TPS/Purchased TPS specification x 100%. If the cluster load is excessively high, it is recommended to upgrade the cluster specifications according to your actual scenarios.

tencent cloud

Selection Overview

Product Form Selection

Product Forms

Product Form Selection Recommendations

Specification Selection