Capability Comparison

Last updated:2026-01-30 14:40:38

Capability Comparison

Last updated: 2026-01-30 14:40:38

TDMQ for MQTT offers various edition specifications to cater to the diverse needs of different business scenarios and scales. The main differences between current versions are as follows:
Edition type
Basic Edition (Currently Not Available for Sale)
Pro Edition
Platinum Edition
TPS specification
2000 and 5000 specifications. TPS units are converted based on billing rules, and excess message sending/receiving will be rejected.
Multiple specification options: 2000-50,000. TPS units are converted based on billing rules, and excess message sending/receiving will be rejected.
Specification options: 50,000 and above TPS, with up to 5 million TPS and 10 million connections available.
TPS units are converted based on billing rules, and excess message sending/receiving will be rejected.
If you require higher specifications for the Platinum Edition, please submit a ticket to contact us.
Resource Isolation
All components are deployed with high availability.
The computing layer is physically dedicated, while the storage layer and other basic version clusters share physical resources and are logically isolated.
All components are deployed with high availability.
The computing layer is physically dedicated, while the storage layer and other Pro Edition Clusters share physical resources and are logically isolated.
All components are physically dedicated and deployed with high availability.
Server-side ReceiveMaximum setting
ReceiveMaximum=16. The server's ReceiveMaximum setting in MQTT 5.0 means the supported number of QoS 1 and 2 Publish Packets the server can process simultaneously. QoS 0 Packets are unlimited. If it exceeds this limit, the consumption request will be rejected.
ReceiveMaximum=1024. The server's ReceiveMaximum setting in MQTT 5.0 means the supported number of QoS=1 and 2 Publish Packets the server can process simultaneously. QoS=0 Packets are unrestricted. If it exceeds this limit, the consumption request will be rejected.
﻿
Maximum number of online client connections
The default ratio of TPS is 1:1 and cannot be adjusted. Client connections will be rejected if the maximum limit is exceeded.
Supports free adjustment, ranging from 1 to 10 times the TPS. Client connections will be rejected if the maximum limit is exceeded.
﻿
Authentication Method
Only supports default passwords and SSL Certificates; the "one device, one certificate" feature is not supported.
Except for passwords and SSL Certificates, it additionally supports autonomous integration with third-party authentication. Currently only supports JWT Authentication, with follow-up integration of more custom external authentication sources.
Supports the "one device, one certificate" feature (manual/automatic registration of device certificates and CA certificates).
﻿
Data plane authorization management
Supports fine-grained authorization policies (client, IP, Topic), with up to 10 concurrent policies.
Supports fine-grained authorization policies (client, IP, Topic), with varying specifications supporting up to 20-50 concurrent policies.
﻿
Send messages via HTTP(S)
Not supported
Supported
﻿
P2P messaging pattern
Not supported
Supported. After the consumer's client ID is known, targeted P2P messaging can be performed.
﻿
﻿
﻿
﻿
﻿
﻿
﻿
﻿

Was this page helpful?

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

Yes

Feedback

Edition type	Basic Edition (Currently Not Available for Sale)	Pro Edition	Platinum Edition
TPS specification	2000 and 5000 specifications. TPS units are converted based on billing rules, and excess message sending/receiving will be rejected.	Multiple specification options: 2000-50,000. TPS units are converted based on billing rules, and excess message sending/receiving will be rejected.	Specification options: 50,000 and above TPS, with up to 5 million TPS and 10 million connections available. TPS units are converted based on billing rules, and excess message sending/receiving will be rejected. If you require higher specifications for the Platinum Edition, please submit a ticket to contact us.
Resource Isolation	All components are deployed with high availability. The computing layer is physically dedicated, while the storage layer and other basic version clusters share physical resources and are logically isolated.	All components are deployed with high availability. The computing layer is physically dedicated, while the storage layer and other Pro Edition Clusters share physical resources and are logically isolated.	All components are physically dedicated and deployed with high availability.
Server-side ReceiveMaximum setting	ReceiveMaximum=16. The server's ReceiveMaximum setting in MQTT 5.0 means the supported number of QoS 1 and 2 Publish Packets the server can process simultaneously. QoS 0 Packets are unlimited. If it exceeds this limit, the consumption request will be rejected.	ReceiveMaximum=1024. The server's ReceiveMaximum setting in MQTT 5.0 means the supported number of QoS=1 and 2 Publish Packets the server can process simultaneously. QoS=0 Packets are unrestricted. If it exceeds this limit, the consumption request will be rejected.
Maximum number of online client connections	The default ratio of TPS is 1:1 and cannot be adjusted. Client connections will be rejected if the maximum limit is exceeded.	Supports free adjustment, ranging from 1 to 10 times the TPS. Client connections will be rejected if the maximum limit is exceeded.
Authentication Method	Only supports default passwords and SSL Certificates; the "one device, one certificate" feature is not supported.	Except for passwords and SSL Certificates, it additionally supports autonomous integration with third-party authentication. Currently only supports JWT Authentication, with follow-up integration of more custom external authentication sources. Supports the "one device, one certificate" feature (manual/automatic registration of device certificates and CA certificates).
Data plane authorization management	Supports fine-grained authorization policies (client, IP, Topic), with up to 10 concurrent policies.	Supports fine-grained authorization policies (client, IP, Topic), with varying specifications supporting up to 20-50 concurrent policies.
Send messages via HTTP(S)	Not supported	Supported
P2P messaging pattern	Not supported	Supported. After the consumer's client ID is known, targeted P2P messaging can be performed.

tencent cloud