TDMQ for RabbitMQ
- Release Notes and Announcements
- Product Introduction
- Relevant Concepts
- Operation Guide
- Cluster Management
- Policy List
- Monitoring alarm
- Tag Management
- Development Guide
- Practical Tutorial
- SDK Documentation
- General References
Billing Overview
Last updated: 2025-03-18 09:59:37
This document describes the billing mode and billable items of TDMQ for RabbitMQ exclusive cluster.
Billing Mode
TDMQ for RabbitMQ exclusive clusters offer two billing options: Monthly Subscription (Prepaid) and Pay-as-You-Go (Postpaid) .
Monthly Subscription is a billing method that requires payment in advance to use resources. When you purchase an exclusive cluster, the system calculates your bill based on the selected cluster specifications and the purchase duration. You need to settle the bill before starting to use the corresponding resources. This billing method is suitable for scenarios where the business traffic peak is relatively stable over different time periods and for long-term usage.
Pay-as-You-Go is a billing method based on the actual usage of the purchased resource specifications. It is mainly suitable for testing or scenarios with uncertain traffic peaks. You can use the resources first and pay later, with fees settled on an hourly basis at the top of each hour.
Billable Items
TDMQ for RabbitMQ exclusive cluster fees are calculated as follows:
Cluster price = computing configuration price + storage configuration price = node unit price number of nodes + storage unit price storage size.
Billable item | Description |
Computing configuration | It refers to the computing service fees. Various node specifications are provided on demand. There are restrictions on the numbers of minimum and maximum nodes. The computing configuration price changes linearly based on the number of nodes. |
Storage configuration | It refers to the storage service fees. You can customize the storage space in increments of 100 GB. The storage configuration price changes linearly based on the storage size. |
Public Network Bandwidth | By default, a 3 Mbps public network bandwidth is provided for free. Billing will apply only to the upgraded portion of the bandwidth. If the public network bandwidth is not upgraded, no fees will be incurred. |
Pricing
The specific price is as displayed on the purchase page. This section describes the performance differences between exclusive cluster specifications.
Computing configuration
Computing configuration fees = node price x number of nodes
Note:
If the number of nodes in current specifications cannot meet your business requirements, you can submit a ticket for assistance.
A single-node cluster does not offer high availability in the production environment and cannot guarantee the SLA. Purchase it with caution.
Minimum number of nodes for multi-AZ: 3
Minimum number of nodes for single AZ: 1
Maximum optional number of nodes: 7 (odd numbers only)
Storage configuration
Storage fees = storage space x storage unit price.
Each exclusive cluster version provides a minimum storage of 200 GB for a single node. You can choose a higher storage space in increments of 100 GB based on your business needs.
Public Network Bandwidth
In the monthly subscription billing mode, the fees for public network bandwidth are as follows:
Region | Price (Unit: USD/Month) | |||||
| For bandwidth less than or equal to 3 Mbps | | | 4 Mbps | 5 Mbps | 6 Mbps and above (n is the Configured Maximum Bandwidth) |
Guangzhou, Shenzhen Finance, Shanghai, Shanghai Finance, Nanjing, Beijing, Chengdu, Chongqing | 0 | | | 13.71 | 17.86 | 29.29 + 11.43 × (n - 6) |
Shanghai Autonomous Driving Cloud | 0 | | | 20.57 | 26.79 | 43.93 + 17.14 ×(n - 6) |
Silicon Valley, Hong Kong (China), Virginia, Taipei (China) | 0 | | | 17.14 | 21.43 | 35.71 + 14.29 ×(n - 6) |
Frankfurt , Singapore | 0 | | | 13.14 | 16.43 | 27.86 + 11.43 ×(n - 6) |
Bangkok, Seoul, Tokyo | 0 | | | 14.29 | 17.86 | 29.86 + 12 × (n - 6) |
Under the pay-as-you-go billing mode, public network bandwidth fees are as follows:
Region | Price (Unit: USD/Hour) | |||||
| For bandwidth less than or equal to 3 Mbps | | | 4 Mbps | 5 Mbps | 6 Mbps and above (n is the upper limit of the configured bandwidth.) |
Guangzhou, Shenzhen Finance, Shanghai, Shanghai Finance, Nanjing, Beijing, Chengdu, and Chongqing | 0 | | | 0.0285 | 0.0373 | 0.0611+ 0.0238 x (n - 6) |
Shanghai Autonomous Driving Cloud | 0 | | | 0.0428 | 0.0559 | 0.0916 + 0.0357 x (n - 6) |
Silicon Valley, Hong Kong (China), Virginia, and Taipei (China) | 0 | | | 0.0358 | 0.0448 | 0.0746 + 0.0298 x (n - 6) |
Frankfurt and Singapore | 0 | | | 0.0273 | 0.0342 | 0.058 + 0.0238 x (n - 6) |
Bangkok, Seoul, and Tokyo | 0 | | | 0.0298 | 0.0375 | 0.0625 + 0.025 x (n - 6) |
Performance Reference
This section describes the performance differences between exclusive cluster nodes of different specifications, to aid in your purchase decision.
The performance of the following specification is our set reference benchmark value. The actual performance will not be lower than this specification, based on the data from user stress testing, and there will be no additional fees for sudden elasticity beyond the specifications.
Message Type: TDMQ for RabbitMQ offers four types of messages: normal messages, persistent messages, priority messages, and delayed messages. Sending or consuming one message is counted as 1 TPS.
Message Size: Measured at 4 KB per 1 TPS, and sizes less than 4 KB are rounded up to 4 KB. The maximum size for a single message is 4 MB.
Node Specification | Single Node Configuration Recommendations (for reference only) | ||
| TPS (Production + Consumption) | Recommended Number of Queues | Recommended Number of Connections |
2-core 4 GB | 750~1250 | 100 | 500 |
4-core 16 GB | 1800~3000 | 200 | 2,500 |
8-core 32 GB | 4500~7500 | 500 | 5,000 |
16-core 32 GB | 9,000-15,000 | 800 | 8,000 |
2-core 4 GB (unavailable for new purchases) | 600~1000 | 100 | 500 |
4-core 8 GB (unavailable for new purchases) | 1500~2500 | 100 | 2000 |
8-core 16 GB (unavailable for new purchases) | 3000~5000 | 200 | 3000 |
Notes on TPS configuration recommendations:
TDMQ for RabbitMQ provides TPS configuration recommendations to assist users in selecting node specifications as a reference.
When the cluster’s production and consumption TPS reach the recommended upper limit, traffic throttling is not triggered. However, to ensure stable cluster operations, it is recommended to follow the suggested TPS values to avoid CPU and memory load issues caused by excessive traffic.
Notes on node specifications marked as sold out and unavalaible for new purchases:
Node specifications marked as sold out indicate that they are no longer available for new purchases or upgrades on the purchase page. However, the management features, renewals, and upgrades of existing clusters with these specifications are not affected. It is recommended to use node specifications that are currently available for sale.
Node specifications marked as unavailable for new purchases will be sold out in the near future. Once sold out, they will no longer be available for new purchases or upgrades to the corresponding node specifications. However, the management features, renewals, and upgrades of existing clusters with these specifications will remain unaffected.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No