This document describes the pricing details and free tier information for each billable item of TDMQ for Apache Pulsar virtual clusters.
Pay-as-You-Go
Pricing of API Calls
TDMQ for Apache Pulsar virtual clusters implement tiered pricing for API calls. API call fee = (Number of message sending API calls + Number of message consumption API calls) x Unit price of API calls.
The following table shows the unit price of API calls (USD/million calls).
|
|
| Guangzhou, Shanghai, Nanjing, Beijing, and Chengdu | Hong Kong (China), Singapore, Seoul, Silicon Valley, Frankfurt | Shenzhen Finance and Shanghai Finance |
Tier 1 | N ≤ 1000 | 0.3 | 0.3 | 0.4 |
Tier 2 | 1000 < N ≤ 5000 | 0.2 | 0.3 | 0.4 |
Tier 3 | 5000 < N ≤ 10000 | 0.2 | 0.2 | 0.3 |
Tier 4 | 10000 < N ≤ 50000 | 0.2 | 0.2 | 0.3 |
Tier 5 | N > 50000 | 0.2 | 0.2 | 0.2 |
The maximum message body size is 5 MB, and the number of API calls is calculated at different rates based on the message size.
|
N ≤ 2KB | 1 |
2KB < N ≤ 4KB | 2 |
4KB < N ≤ 16KB | 4 |
16KB < N ≤ 100KB | 16 |
100KB < N ≤ 1MB | 64 |
1MB < N ≤ 5MB | 256 |
For example, a 10 KB message (publishing or subscription) request will be charged as 4 API calls.
Note:
The number of API calls for message consumption refers to the number of messages pushed by the broker to consumers. This value may be numerically greater than the number of messages actually acknowledged by consumers. Scenarios where this occurs include:
1. When a large message backlog exists, consumers prefetch a certain number of messages during connection. Multiple unacknowledged messages (unack) are recorded as multiple API calls for message consumption. In this case, the number of API calls for message consumption is greater than the number of messages actually acknowledged by consumers.
2. When tag messages are consumed, multiple consumers are usually started. In this case, the number of API calls for message consumption is greater than the number of messages actually acknowledged by consumers.
Message Storage Pricing
TDMQ for Apache Pulsar virtual clusters implement linear pricing for message storage. Message storage fee = Message storage size x Unit price of message storage.
Note:
Pulsar stores a message in three replicas by default. Therefore, the billable storage size is approximately three times of the total message size.
The following table shows the unit price of message storage (Unit: USD/GB/hour).
Note:
1. When the message retention policy is set to persistent retention, even if a message is consumed, it will still be persistently stored for the maximum retention time, resulting in additional message storage fees.
2. In Pulsar, message data is stored on the Bookie storage node of the BookKeeper cluster in the form of a ledger. Even if the consume-and-delete policy is configured, when the ledger is enabled, the async cleaner will not clear the message data. If some messages are not consumed for a long time, other messages in the same ledger may keep consuming the storage space, resulting in additional message storage fees.
Partition Topic Usage Pricing
TDMQ for Apache Pulsar virtual clusters implement linear pricing for partition topic usage. Partition topic usage fee = Number of partition topics x Unit price of partition topic usage.
The number of partition topics in Pulsar refers to the sum of all partitions of all topics. If there are two topics with 3 partitions each, the number of partition topics is 2 x 3 = 6.
The following table shows the unit price of partition topic usage (Unit: USD/unit/day).
|
Unit Price (USD/Unit/Day) | 0.0251 | 0.0327 | 0.0402 |
Note:
The billing cycle for partition topic usage in TDMQ for Apache Pulsar virtual clusters is one day. A partition topic created at any time on a natural day will incur a full day's fees on the next natural day, even if its actual usage duration is less than 24 hours.
Free Tiers
TDMQ for Apache Pulsar offers certain free tiers for pay-as-you-go billable items. The following table shows the free tiers offered to each root account in each region for pay-as-you-go clusters.
|
| | Accumulated monthly by region |
| | Accumulated monthly by region |
| | Accumulated monthly by region |
The free tiers will be used first to deduct the cumulative usage of all clusters in each region under each root account, and they are shared between different clusters within the same region.