This document describes the specifications, billing modes, and pricing of TDMQ for MQTT clusters.
Product Series
TDMQ for MQTT currently offers multiple edition specifications. For differences between editions, see Product Series. Each specification provides two billing modes: yearly/monthly subscription (prepaid) and pay-as-you-go (postpaid). Billing Mode
TDMQ for MQTT clusters support two billing modes: yearly/monthly subscription (prepaid) and pay-as-you-go (postpaid). The differences between billing modes are as follows:
|
Billing Description | Select specified specifications and prepay for a certain period before you can use the resources. | Select specified specifications to create a cluster and pay after using the resources. |
Billing Cycle | Billed based on the purchased duration of the order. | Billed hourly, with daily settlement. Usage under one hour is rounded up. |
Scenario | Suitable for scenarios with stable business scale and long-term usage, offering discounted pricing to help reduce long-term costs. | Suitable for short-term scenarios such as testing or uncertain traffic peaks, billed on a pay-as-you-go basis to avoid idle resource waste. |
Changing Billing Mode | Not supported. | Not supported. |
Changing Cluster Specification | Supported. | Supported. |
Cluster Specification Downgrade | Supported. | Supported. |
Billing Items
TDMQ for MQTT is sold as clusters with the following billing items:
|
Compute Specifications | Yes | Yearly/Monthly subscription/Pay-as-you-go | Provides multiple TPS specifications. Each specification defines the number of client connections for the cluster, the maximum number of separately purchasable connections, and the message read/write TPS capacity limit. |
Number of Connections | No | Yearly/Monthly subscription/Pay-as-you-go | If the number of connections included in your current MQTT cluster specification does not meet your requirements, you can purchase additional connections separately. |
Public Network Traffic Fees | No | Pay-as-you-go | After public network access is enabled, fees are charged based on actual traffic usage, billed by the total amount of data transmitted over the public network (in GB). Settlements occur hourly, with charges calculated based on actual usage. You can disable this feature at any time. If public network access is not enabled, no fees are incurred. |
Pricing
Computing Specification Fees
The compute specifications provided by TDMQ for MQTT and the performance limits for each specification are listed in the following table:
TPS Specification: The TPS capacity provided by the MQTT cluster, including the sum of production TPS and consumption TPS.
Number of Connections: The sum of online clients and offline clients with preserved sessions at any given moment.
Notes:
When the MQTT protocol is used to send and receive messages, each message send/receive operation is counted as 1 basic unit of measurement. TPS specifications are comprehensively calculated based on the sum of three dimensions: message service QoS, message storage resource usage, and message body size. Specifically:
Message Service QoS
Message service QoS = 0 is calculated as 1 TPS.
Message service QoS = 1 is calculated as 2 TPS.
Message service QoS = 2 is calculated as 5 TPS.
Storage Resource Usage
When messages use the Will feature and Retain feature, they require additional broker storage resources. Therefore, when you configure the Will and Retain features, an additional 10 TPS is calculated for each.
Message Body Size
Each message is calculated in units of 4 KB. If the size is less than 4 KB, no additional TPS is calculated. For every additional 4 KB exceeded, an additional 1 TPS is calculated.
For example, a cluster has 3 clients connected at the same time. The cluster sends a QoS = 1 message to the first client with a message body size of 64 KB. The corresponding cluster production TPS is calculated as 2 + ⌈64/4 - 1⌉ = 17 TPS. The cluster receives a QoS = 2 message with the Retain feature enabled from the second client with a message body size of 32 KB. The corresponding cluster message TPS is calculated as 5 + 10 + ⌈32/4 - 1⌉ = 22 TPS. The third client connects to the cluster and enables the Will feature, with an additional 10 TPS. The comprehensive cluster TPS at this point is calculated as 17 + 22 + 10 = 49 TPS.
|
Basic Edition (no longer available for new purchases) | 2000 | 2000 | Connections cannot be purchased separately. | Specific pricing is subject to the actual price on the product Sales page. |
| 5000 | 5000 |
|
|
Pro Edition | 2000 | 2000 | 20000 |
|
| 5000 | 5000 | 50000 |
|
| 10000 | 10000 | 100000 |
|
| 20000 | 20000 | 200000 |
|
| 50000 | 50000 | 500000 |
|
Connection Fees
After selecting the TPS size, if the complimentary connections included in the corresponding specification do not meet your requirements, you can purchase additional connections separately. Connections are purchased in units based on the cluster TPS specification (1 unit = 1x TPS specification). The pricing is as follows:
|
Pro Edition | 1x TPS specification 2x TPS specification 5x TPS specification 10x TPS specification | Specific pricing is subject to the actual price on the product Sales page. |
Basic Edition (no longer available for new purchases) | Connections cannot be purchased separately. |
|
Public Network Traffic Fees
Notes:
Billed traffic is outbound traffic (Mbps), that is, traffic from the Cloud Load Balancer (CLB) to the public network.
To prevent high costs caused by sudden traffic bursts, you can specify a bandwidth cap. If the traffic exceeds the bandwidth cap, packets are discarded by default, and no fees are charged.
Traffic is measured in binary units: 1 TB = 1024 GB, 1 GB = 1024 MB.
|
Guangzhou/Shanghai/Beijing/Nanjing | 0.14 |
Shanghai Self-driving Driving Cloud | 0.23 |
Singapore/Silicon Valley/Frankfurt | 0.19 |
Purchase Methods