TDMQ for RocketMQ 4.x general clusters support the yearly/monthly subscription (prepaid) billing mode. For details on the billing mode and the composition of cluster billable items, see Billing Overview. This document mainly introduces the pricing of each billable item of TDMQ for RocketMQ 4.x general clusters. Computing Configuration Fee
TDMQ for RocketMQ 4.x general clusters use message sending and receiving TPS to measure the computing capacity. The TPS size (with a step size of 4,000 TPS) can be customized. The computing fee is calculated based on the TPS specifications and usage duration.
TPS Calculation Rules
TPS is calculated in two dimensions: message type and message size.
Message type: TDMQ for RocketMQ supports four message types: normal messages, scheduled and delayed messages, transactional messages, and ordered messages. The last three message types are all advanced feature messages.
Normal messages: The message TPS is calculated as 1 time/second each time a normal message is sent or consumed, regardless of whether the message is sent successfully or consumed successfully.
Advanced feature messages: The message TPS is calculated as 5 times/second each time an advanced feature message is sent or consumed. For example, if two transactional messages are sent once and one transactional message is consumed for a topic, the message sending and receiving TPS is calculated as follows: 2 x 5 + 1 x 5 = 15 times/second.
Message size:
Message size is measured in units of 4 KB. If a message is less than 4 KB in size, it will be counted as 4 KB. For example, if a message request is 18 KB in size, the message sending TPS is calculated as follows: ⌈18/4⌉ = 5 times/second.
⌈ ⌉ means rounding up to the nearest integer.
Pricing
TPS specifications include the total number of production and consumption messages. Traffic exceeding the cluster TPS specifications will be strictly throttled.
|
8000 | 628.57 | 817.14 | 1005.71 |
12000 | 857.14 | 1114.28 | 1371.42 |
16000 | 1085.71 | 1411.42 | 1737.13 |
20000 | 1314.28 | 1708.56 | 2102.84 |
24000 | 1542.85 | 2005.7 | 2468.55 |
28000 | 1771.42 | 2302.84 | 2834.26 |
32000 | 1999.99 | 2599.98 | 3199.97 |
36000 | 2228.56 | 2897.12 | 3565.68 |
40000 | 2457.13 | 3194.26 | 3931.39 |
44000 | 2685.7 | 3491.4 | 4297.1 |
48000 | 2914.27 | 3788.54 | 4662.81 |
52000 | 3142.84 | 4085.68 | 5028.52 |
56000 | 3371.41 | 4382.82 | 5394.23 |
60000 | 3599.98 | 4679.96 | 5759.94 |
64000 | 3828.55 | 4977.1 | 6125.65 |
68000 | 4057.12 | 5274.24 | 6491.36 |
72000 | 4285.69 | 5571.38 | 6857.07 |
76000 | 4514.26 | 5868.52 | 7222.78 |
80000 | 4742.83 | 6165.66 | 7588.49 |
Storage Configuration Fee
The starting storage space for general clusters is 200 GB. You can select higher storage space based on your business requirements (with a step size of 20 GB). Storage fee varies linearly with the storage size and usage duration.
Topic Fee Incurred for the Portion Exceeding Specifications
Each type of cluster specifications supports a different free tier of topics. Any portion exceeding the free tier will be charged based on tiered pricing. If the number of topics you require exceeds the upper limit of the current cluster specifications, it is recommended that you upgrade your computing cluster specifications. By default, the number of groups and the number of topics are a 10:1 ratio. You can modify the topic quota to adjust the group quota.
Note:
The number of topics here only includes those created in the console. Topics corresponding to dead letter queues and retry queues do not consume the quota.
Topic Free Tiers and Upper Limits
|
8000 | 400 | 2000 |
12000 | 600 | 2000 |
16000 | 800 | 2000 |
20000 | 1000 | 2000 |
24000 | 1200 | 2000 |
28000 | 1400 | 2000 |
32000 | 1600 | 2000 |
36000 | 1800 | 2000 |
40000 | 2000 | 2000 |
44000 | 2000 | 2000 |
48000 | 2000 | 2000 |
52000 | 2000 | 2000 |
56000 | 2000 | 2000 |
60000 | 2000 | 2000 |
64000 | 2000 | 2000 |
68000 | 2000 | 2000 |
72000 | 2000 | 2000 |
76000 | 2000 | 2000 |
80000 | 2000 | 2000 |
Topic Pricing for Additional Purchases
|
0-100 | 1.7 | 2.23 | 2.74 |
101-200 | 1.43 | 1.86 | 2.28 |
201-500 | 1.14 | 1.49 | 1.83 |
501-1500 | 0.86 | 1.11 | 1.37 |
1501-2000 | 0.57 | 0.74 | 0.91 |
More than 2,000 | 0.38 | 0.37 | 0.46 |
Billing example:
Customer A purchased a TDMQ for RocketMQ 4.x general cluster with 8,000 TPS in the Guangzhou region, requiring 900 topics. The general cluster with 8,000 TPS supports a default free tier of 400 topics. Therefore, the excess number of topics is 500. Based on the tiered pricing structure above, the additional topic fee is calculated as follows: 1.7 x 100 + 1.43 x 100 + 1.14 x (500 – 200) = USD 655/month.
Public Network Bandwidth Pricing
After the public network bandwidth is enabled, fees will be incurred based on the usage duration of the public network bandwidth. Once it is enabled, you can disable it on the Cluster Management page. If public network access is not enabled, no fees will be incurred.
The public network of 4.x exclusive clusters supports two billing modes: by hourly bandwidth and by traffic usage.
Postpaid by Hour
This billing mode is charged based on the public network transmission rate (unit: Mbps) and is settled on an hourly basis. During the settlement, fees are calculated based on the actual usage hours.
|
| 1Mbps - 5Mbps | 6 Mbps and higher |
Nanjing, Shanghai, Guangzhou, Qingyuan, Beijing, Hong Kong (China), and Shanghai Finance | 0.0057 | 0.02 |
Singapore, Virginia, and Silicon Valley | 0.005 | 0.017 |
Jakarta and Shanghai Autonomous Driving Cloud | 0.0086 | 0.03 |
Pay-by-Traffic
Note:
The current billed traffic is outbound traffic (Mbps), indicating the traffic from Cloud Load Balancer (CLB) to the public network.
To prevent high costs caused by sudden traffic bursts, you can specify an upper limit on the bandwidth. If the traffic volume exceeds the upper limit of the bandwidth, packets will be discarded by default, and no fees will be charged.
The unit conversion scale for traffic is 1024. That is, 1 TB = 1024 GB, and 1 GB = 1024 MB.
|
Nanjing, Shanghai, Guangzhou, Qingyuan, and Beijing | 0.1429 |
Shanghai Finance | 0.2286 |
Shanghai Autonomous Driving Cloud | 0.1714 |
Hong Kong (China), Singapore, Silicon Valley, Virginia, and Jakarta | 0.1857 |