- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- RocketMQ 5.x
- RocketMQ 4.x
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- SDK Documentation
- Migration to Cloud
- API Documentation
- FAQs
- TDMQ FOR ROCKETMQ SERVICE LEVEL AGREEMENT
- Contact Us
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- RocketMQ 5.x
- RocketMQ 4.x
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- SDK Documentation
- Migration to Cloud
- API Documentation
- FAQs
- TDMQ FOR ROCKETMQ SERVICE LEVEL AGREEMENT
- Contact Us
TDMQ for RocketMQ has ended its public beta of virtual clusters on December 28, 2022 and will start billing for such clusters. This document describes the billing mode and billable items of a TDMQ for RocketMQ virtual cluster.
Available Regions
Virtual cluster is currently supported in the following regions:
Region | Value |
Guangzhou | ap-guangzhou |
Shanghai | ap-shanghai |
Shanghai Finance | ap-shanghai-fsi |
Beijing | ap-beijing |
Nanjing | ap-nanjing |
Beijing Finance | ap-beijing-fsi |
Hong Kong (China) | ap-hongkong |
Singapore | ap-singapore |
Silicon Valley | na-siliconvalley |
Frankfurt | eu-frankfurt |
Seoul | ap-seoul |
Mumbai | ap-mumbai |
Virginia | na-ashburn |
Jakarta | ap-jakarta |
Billing Mode
The billing method of a TDMQ for RocketMQ virtual cluster is **pay-as-you-go (postpaid)**. Pay-as-you-go is a payment method based on the actual usage of the resource specifications you purchased, which is suitable for testing or scenarios with unpredictable traffic peaks. You can use resources before making payment, and the fee is settled on every clock-hour.
Billable Items
TDMQ for RocketMQ virtual clusters are sold in the form of clusters, and the billing formula in the pay-as-you-go mode is as follows:
Total fee = API calls fee + topic usage fee = (number of API calls for sending messages + number of API calls for consuming messages) x unit price of API calls + number of topics x number of days x unit price of topic.
Billable Items | Billing Rules |
API calls fee | The calculation rules for the number of API calls are based on message type and message size. Message type: TDMQ for RocketMQ has four message types: general message, scheduled and delayed message, transactional message, and sequential message. Except general messages, the other three message types are advanced messages. General message: Sending or consuming one general message is counted as one API call regardless of whether it is successfully sent or consumed, and the API call will be billed once initiated. Advanced messages: Sending or consuming one advanced message is counted as five API calls. For example, if a topic sends 2 transactional messages once and consumes 1 transactional message, the number of API calls is calculated as: 2×5+1×5=15 calls. Message size: The maximum size of a single message is 4 MB, with 4 KB as the unit of measurement. A message that is less than 4 KB is calculated to be 4 KB. For example, the request of an 18 KB message will be billed as ⌈18/4⌉=5 API calls. ⌈ ⌉ means rounding up to the nearest integer. |
Topic usage fee | The topic unit price will change on a tier basis based on the number of API calls generated by each topic on the day. Each topic will be charged a resource usage fee every day. The daily topic resource usage fee is the sum of the fees generated by all topics on the day. No matter whether the topic has sent or received messages on the day, it will be billed once. |
Pricing
Free Tier
Each root account has a monthly quota of 20 million free API calls.
Note
The free quota is temporarily provided during the new product promotion period. Before the official billing, you will be notified by announcements, SMS, Message Center, and emails.
API Calls Fee
Pricing Tier | Number of Calls (Billion Calls/Month) | Unit Price (USD/Million Calls) for Public Cloud | ||
| | Regions in Chinese Mainland | Regions Outside Chinese Mainland | Finance Zone |
First tier | 0–10 | 0.26 | 0.33 | 0.41 |
Second tier | 10–50 | 0.21 | 0.13 | 0.29 |
Third tier | 50–500 | 0.17 | 0.23 | 0.29 |
Fourth tier | > 500 | 0.14 | 0.19 | 0.23 |
Note
The above tiers are based on the Tencent Cloud account (UIN) and the cumulative number of API calls by billing period (monthly).
Billing example
Suppose your instance resides in Guangzhou region, the daily message sending and receiving is as follows:
50 million general messages are produced, the number of message consumption is 70 million times (including the number of retries upon message delivery failures), and the size of each message is 20 KB.
30 million transactional messages are produced, the number of message consumption is 30 million times, and the size of each message is 4 KB.
10 million delayed messages are produced, the number of message consumption is 10 million times, and the size of each message is 2 KB.
Then, the number of API calls generated on the day is caculated as: (50 million + 70 million) × ⌈20/4⌉ + (30 million + 30 million) × 5 × ⌈4/4⌉ + (10 million + 10 million) × 5 × ⌈2/4⌉ = 1 billion calls.
If 1 billion API calls are generated every day in September, the incurred API call fees are as follows:
On September 1, the number of API calls is 1 billion, and the cumulative number of API calls in the month is 1 billion, which falls within the first tier. The unit price is 0.26 USD, and the fee charged is 10 × 0.26 × 100 = 260 US dollars (100 means 101 million100 (i.e.,1 billion), the unit price is charged per million calls).
On September 2, the number of API calls is 1 billion, and the cumulative number of API calls in the month is 2 billion, which falls within the second tier. The unit price is 0.21 US dollars, and the fee charged is 10 × 0.21 × 100 = 210 US dollars (100 means 101 million100 (i.e.,1 billion), the unit price is charged per million calls).
On September 3, the number of API calls is 1 billion, and the cumulative number of API calls in the month is 3 billion, which falls within the second tier. The unit price is 0.21 USD, and the fee charged is 10 × 0.21 × 100 = 210 US dollars (100 means 101 million100 (i.e.,1 billion), the unit price is charged per million calls).
September 4 and the remaining September days are calculated in a similar manner.
On October 1, the cumulative number of API calls will start from 0.
Topic Usage Fee
The topic unit price will change on a tier basis based on the number of API calls generated by each topic on the day. The daily topic resource usage fee is the sum of the fees generated by all topics on the day. A topic created less than one day will still be charged because it is considered to have existed for a day.
Note
Since the billing cycle is calculated from 0 o'clock, if you delete the topic resources on a day, the resource usage fee will still be charged on the day, so the fee will still be displayed in the bill of next day; but no fees will be charged after that.
Pricing Tier | Number of Calls (10,000 Times/Topic/Day) | Unit Price for Public Cloud (USD/Topic/Day) | ||
| | Regions in Chinese Mainland | Regions Outside Chinese Mainland | Finance Zone |
First tier | 0–100 | 0.26 | 0.33 | 0.41 |
Second tier | 100–1000 | 0.13 | 0.17 | 0.21 |
Third tier | > 1000 | 0 | 0 | 0 |
Billing example
Suppose your instance resides in Guangzhou region, and you have created a total of three topics.
Topic 1 has 200,000 API calls on a day, which falls within the first tier, and the topic usage fee will be 0.26 USD on the day.
Topic 2 has 2 million API calls on the same day, which falls within the second tier, and the topic usage fee will be 0.13 USD on the day.
Topic 3 has 500,000 API calls on the same day, which falls within the first tier, and the topic usage fee will be 0.26 USD on the day.
Then, the sum of topic usage fees charged on the day = 0.26 + 0.13 + 0.26 = 0.65 USD.
Yes
No
Was this page helpful?