tencent cloud

TDMQ for RocketMQ

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Introduction and Selection of the TDMQ Product Series
What Is TDMQ for RocketMQ
Strengths
Scenarios
Product Series
Comparison with Open-Source RocketMQ
High Availability
Quotas and Limits
Supported Regions
Basic Concepts
Billing
Billing Overview
Pricing
Billing Examples
Pay-as-you-go Switch to Monthly Subscription (5.x)
Renewal
Viewing Consumption Details
Refund
Overdue Payments
Getting Started
Getting Started Guide
Preparations
Step 1: Creating TDMQ for RocketMQ Resources
Step 2: Using the SDK to Send and Receive Messages (Recommended)
Step 2: Running the TDMQ for RocketMQ Client (Optional)
Step 3: Querying Messages
Step 4: Deleting Resources
User Guide
Usage Process Guide
Configuring Account Permissions
Creating the Cluster
Configuring the Namespace
Configuring the Topic
Configuring the Group
Connecting to the Cluster
Managing Messages
Managing the Cluster
Viewing Monitoring Data and Configuring Alarms
Cross-Cluster Message Replication
Use Cases
Naming Conventions for Common Concepts of TDMQ for RocketMQ
RocketMQ Client Use Cases
RocketMQ Performance Load Testing and Capacity Assessment
Access over HTTP
Client Risk Descriptions and Update Guide
Migration Guide for TencentCloud API Operations Related to RocketMQ 4.x Cluster Roles
Migration Guide
Disruptive Migration
Seamless Migration
Developer Guide
Message Types
Message Filtering
Message Retries
POP Consumption Mode (5.x)
Clustering Consumption and Broadcasting Consumption
Subscription Relationship Consistency
Traffic Throttling
​​API Reference(5.x)
History
API Category
Making API Requests
Topic APIs
Consumer Group APIs
Message APIs
Role Authentication APIs
Hitless Migration APIs
Cloud Migration APIs
Cluster APIs
Data Types
Error Codes
​​API Reference(4.x)
SDK Reference
SDK Overview
5.x SDK
4.x SDK
Security and Compliance
Permission Management
CloudAudit
Deletion Protection
FAQs
4.x Instance FAQs
Agreements
TDMQ for RocketMQ Service Level Agreement
Contact Us
DocumentaçãoTDMQ for RocketMQBillingPricing4.x Virtual Clusters (Discontinued)

4.x Virtual Clusters (Discontinued)

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2026-01-23 17:16:37
This document introduces the billing modes, billable items, and other information about TDMQ for RocketMQ (virtual clusters).

Billing Modes

TDMQ for RocketMQ virtual clusters use the pay-as-you-go (postpaid) billing mode. Pay-as-you-go is a billing mode that charges based on the actual usage of purchased resource specifications. It is primarily suitable for testing or scenarios with uncertain traffic peaks. You can pay after using resources, with fees settled hourly on the hour.

Billable Items

TDMQ for RocketMQ virtual clusters are sold in the form of clusters. The formula for the pay-as-you-go billing mode is as follows: 
Total fees = API call fee + Topic resource usage fee = (Number of API calls for message sending + Number of API calls for message consumption) x API call unit price + Number of topics x Number of days x Topic unit price
Billable Item
Billing Rule
API call fee
The number of API calls 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: One API call is counted each time a normal message is sent or consumed. No matter whether the message is sent or consumed successfully, the API call will be charged as long as it is initiated.
Advanced feature messages: Five API calls are counted 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 number of API calls is calculated as follows: 2 x 5 + 1 x 5 = 15.
Message size:
The maximum size of a single message is 4 MB, and the 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 number of API calls is calculated as follows: ⌈18/4⌉ = 5. ⌈ ⌉ means rounding up to the nearest integer.
Topic resource usage fee
The billing unit price of topics changes in steps according to the number of API calls generated for each topic on the day. The resource usage fee is charged once a day for each topic. The daily topic resource usage fee is the sum of the fees generated for all topics on the day. No matter whether message sending and receiving occur for a topic on the day, a fee will be incurred.

Pricing

Free Tiers

Each root account has a free tier of 20 million API calls per month.
Note:
This free tier is temporarily provided during the promotional period for new products. Before official charging starts, notifications will be sent through announcements, Short Message Service (SMS), the Message center, and emails.

API Call Prices

Billing Tier
Number of Calls (100 Million Calls/Month)
Unit Price in Public Cloud (USD/Million Calls)
Chinese Mainland
Outside the Chinese Mainland
Financial Zone
Tier 1
0~10
0.26
0.33
0.41
Tier 2
10~50
0.21
0.13
0.29
Tier 3
50~500
0.17
0.23
0.29
Tier 4
More than 500
0.14
0.19
0.23
Note:
The number of API calls in the above tiers are accumulated based on the Tencent Cloud account (UIN) dimension and monthly billing cycle.
Billing Examples
Assume that your instance is located in the Guangzhou region, with the daily message sending and receiving as follows:
A total of 50 million normal messages are produced, the number of message consumption times is 70 million (including retries for failed message deliveries), and the size of each message is 20 KB.
A total of 30 million transactional messages are produced, the number of message consumption times is 30 million, and the size of each message is 4 KB.
A total of 10 million delayed messages are produced, the number of message consumption times is 10 million, and the size of each message is 2 KB.
Then, the number of API calls generated in a day is calculated as follows: (50 million + 70 million) x ⌈20/4⌉ + (30 million + 30 million) x 5 x ⌈4/4⌉ + (10 million + 10 million) x 5 x ⌈2/4⌉ = 1 billion calls.

If 1 billion API calls are generated every day in September, the API call fee incurred is calculated as follows:
The number of API calls on September 1 was 1 billion, and the cumulative number of API calls in the month was 1 billion. This falls within the range of tier 1, and the unit price is USD 0.26. Therefore, the API call fee is charged as follows: 10 x 0.26 x 100 = USD 260 (100 means 1 billion = 1 million x 100, billed per million calls).
The number of API calls was 1 billion on September 2, and the cumulative number of API calls in the month was 2 billion. This falls within the range of tier 2, and the unit price is USD 0.21. Therefore, the API call fee is charged as follows: 10 x 0.21 x 100 = USD 210 (100 means 1 billion = 1 million x 100, billed per million calls).
The number of API calls was 1 billion on September 3, and the cumulative number of API calls in the month was 3 billion. This falls within the range of tier 2, and the unit price is USD 0.21. Therefore, the API call fee is charged as follows: 10 x 0.21 x 100 = USD 210 (100 means 1 billion = 1 million x 100, billed per million calls).
The API call fee on September 4 and the remaining days of the month is calculated in a similar method.
On October 1, the number of API calls will start counting from zero.

Topic Resource Usage Fee

The billing unit price of topics varies based on the tiered pricing of the number of API calls generated for each topic on the day. The daily topic resource usage fee is the sum of all fees incurred for topics on the day. Topics created for less than one day are billed as one day.
Note:
The billing cycle starts at 00:00. Therefore, if you delete topic resources on the same day, the resource usage fee for that day will still be charged and reflected on the bill on the next day. No further charges will be incurred thereafter.
Billing Tier
Number of Calls (Ten Thousand Calls per Topic per Day)
Unit Price in Public Cloud (USD per Topic per Day)
Chinese Mainland
Outside the Chinese Mainland
Financial Zone
Tier 1
0~100
0.26
0.33
0.41
Tier 2
100~1000
0.13
0.17
0.21
Tier 3
More than 1,000
0
0
0
Billing Examples
Assume that your instance is located in the Guangzhou region, and you have created 3 topics.
A total of 200,000 API calls are generated for topic 1 on the day, falling within the range of tier 1. Therefore, the resource usage fee for the day is USD 0.26.
A total of 2 million API calls are generated for topic 2 on the day, falling within the range of tier 2. Therefore, the resource usage fee for the day is USD 0.13.
A total of 500,000 API calls are generated for topic 3 on the day, falling within the range of tier 1. Therefore, the resource usage fee for the day is USD 0.26.
Therefore, the total resource usage fee for topics on the day is calculated as follows: 0.26 + 0.13 + 0.26 = USD 0.65.

Ajuda e Suporte

Esta página foi útil?

comentários