Messaging is a basic feature provided by Message Queue for Apache RocketMQ. After you activate Message Queue for Apache RocketMQ, the messaging feature is enabled by default. This topic describes the pricing details of the messaging feature provided by Message Queue for Apache RocketMQ and provides billing examples.
Standard Edition instances
Standard Edition instances are billed on a pay-as-you-go basis. Standard Edition instances are suitable for scenarios in which the number of messages is small or greatly fluctuates. You are charged only for the messages that are transmitted and the resources that are used. This improves resource utilization.
Free quotas
Standard Edition instances of Message Queue for Apache RocketMQ are billed on a pay-as-you-go basis and provide free quotas for specific items. However, you may be charged for the items in the future. If the items are no longer free of charge, Alibaba Cloud will notify you by text message, Alibaba Cloud announcement, or internal message.
- Message accumulation
- The first 20 million API calls that are initiated across all regions each month.
Billable items
The messaging fee for a Standard Edition instance is calculated by using the following formula.
The fee for API calls is calculated by using the following formula: API call fee = (Number of API calls to send messages + Number of API calls to subscribe to messages) × Price for an API call.
You are charged based on the total number of API calls each month. Tiered pricing is used to calculate the fee, and the unit price for API calls also varies based on the region.
- When you initiate an API call to send or subscribe to one normal message, the system counts this operation as one API call regardless of whether the call is successful.
- The number of API calls that are required to send and subscribe to a featured message is counted as five times the number of API calls that are required to send and subscribe to a normal message. For example, if you send a transactional message once and subscribe to the message twice, the number of API calls is 15 based on the following formula: 1 × 5 + 2 × 5 = 15.
- The maximum size of a message body is 4 MB. The size of the message that is transmitted in each API call is 4 KB. For example, if you send or subscribe to a 16 KB message, your instance is billed for four API calls based on the following formula: 16/4 = 4.
The fee for topic usage is calculated by using the following formula: Topic usage fee = Usage fee for a single topic each day × Number of topics × Number of days
You are charged a topic usage fee for each topic once a day. The price for topics varies based on the number of API calls that are made by the topic.
API call fee
- Prices at different tiers
Table 1. API call fee Billing tier Number of API calls (100 million calls/month) Unit price (USD/1 million calls) China (Hong Kong), Singapore, Japan (Tokyo), and UAE (Dubai) Malaysia (Kuala Lumpur), India (Mumbai), Indonesia (Jakarta), and Philippines (Manila) China (Shanghai), Australia (Sydney), US (Virginia), US (Silicon Valley), Germany (Frankfurt), and UK (London) First tier 0‒10 0.45 0.42 0.31 Second tier 10‒50 0.41 0.38 0.28 Third tier 50‒100 0.34 0.31 0.23 Fourth tier 100‒500 0.3 0.27 0.20 Fifth tier More than 500 0.27 0.25 0.19 - Rules for tiered pricing
The tiered pricing schedule is based on the total number of API calls that are made by an Alibaba Cloud account each month.
NoteIf an Alibaba Cloud account authorizes another Alibaba Cloud account by using a role, the bill is charged to the authorizing Alibaba Cloud account. If you use an Alibaba Cloud account to authorize RAM users in the Alibaba Cloud account, the bill is charged to the Alibaba Cloud account.
- Example on calculating the number of API calls
- A topic produces 7 million normal messages per day, the number of times for message consumption is estimated to be 8 million considering that a topic may be subscribed to by multiple groups and the messages may be retried, and the size of each message is 40 KB.
- The topic also produces 3 million featured messages per day, the number of times for message consumption is 3 million, and the size of each message is 2 KB.
The number of API calls that are initiated to send and receive messages per day is calculated based on the following formula: Number of API calls = (Number of produced normal messages + number of consumed normal messages) × Multiplier for message size + (Number of produced featured messages + Number of consumed featured messages) × 5 × Multiplier for message size. Therefore, the total number of API calls that are initiated to send and receive messages per day is 180 million based on the following equation: (7 million + 8 million) × ⌈40/4⌉ + (3 million + 3 million) × 5 × ⌈2/4⌉ = 180 million.
Note ⌈ ⌉ indicates that the number is rounded up to the smallest integer that is greater than or equal to the value. - Example on calculating the API call fee
The following table describes the total number of API calls and the tiered pricing schedule for an instance that resides in the China (Shanghai) region and produces 500 million API calls per day.
Item First day of a month Second day of a month Third day of a month Fourth day of a month ... Eleventh day of a month ... Number of API calls 500 million 500 million 500 million 500 million ... 500 million ... Total API calls per month 500 million 1 billion 1.5 billion 2 billion ... 5.5 billion ... Unit price (USD/1 million calls) 0.31 (first tier) 0.31 (first tier) 0.28 (second tier) 0.28 (second tier) ... 0.23 (third tier) ... Fees for the current day (USD) 155 155 140 140 ... 115 ...
Topic usage fee
- Tiered unit price
Table 2. Topic usage fee Billing tier Number of API calls (100 million calls/topic/day) Unit price (USD/topic/day) China (Hong Kong), Singapore, Japan (Tokyo), and UAE (Dubai) Malaysia (Kuala Lumpur), India (Mumbai), Indonesia (Jakarta), and Philippines (Manila) China (Shanghai), Australia (Sydney), US (Virginia), US (Silicon Valley), Germany (Frankfurt), and UK (London) First tier 0‒100 0.45 0.42 0.31 Second tier 100‒500 0.34 0.31 0.23 Third tier 500‒1,000 0.11 0.11 0.08 Fourth tier More than 1,000 0 0 0 - Rules for tiered pricing
The tiered pricing schedule is based on the total number of API calls that are made by each topic every day.
NoteIf an Alibaba Cloud account authorizes another Alibaba Cloud account by using a role, the bill is charged to the authorizing Alibaba Cloud account. If you use an Alibaba Cloud account to authorize RAM users in the Alibaba Cloud account, the bill is charged to the Alibaba Cloud account.
- Example on calculating the topic usage fee
In this example, an instance that resides in the China (Shanghai) region is used, and several topics are created on the instance.
You are charged a topic usage fee for each topic once a day. The daily topic usage fee is the sum of the fees that are generated by all topics per day.
Topic First day of a month Second day of a month Third day of a month ... Topic_1 If the number of API calls on the day is 100,000, the fee falls in the first tier.
Topic usage fee: USD 0.31.
If the number of API calls on the day is 1.2 million, the fee falls in the second tier.
Topic usage fee: USD 0.23.
If the number of API calls on the day is 300,000, the fee falls in the first tier.
Topic usage fee: USD 0.31.
... Topic_2 If the number of API calls on the day is 5.5 million, the fee falls in the third tier.
Topic usage fee: USD 0.08.
If the number of API calls on the day is 800,000 million, the fee falls in the first tier.
Topic usage fee: USD 0.31.
If the number of API calls on the day is 1 million, the fee falls in the first tier.
Topic usage fee: USD 0.31.
... ... ... ... ... ... Topic_n ... ... ... ...
Enterprise Platinum Edition instances
Enterprise Platinum Edition instances are billed on a subscription basis. The instances are suitable for scenarios in which the service level agreement (SLA) requirements are high or the number of messages is large. The subscription billing method is used to reserve resources in advance. This helps reduce costs.
Billable items
- Fee for the selected specification that provides maximum TPS: The maximum TPS specifies the total number of messages that can be sent and subscribed to per second.
The maximum size of a message body is 4 MB. The size of the message that is transmitted in each API call is 4 KB. If 5,000 messages are sent per second, 5,000 messages are delivered per second, and the average body size for each message is 16 KB, the maximum TPS is 40,000 messages per second based on the following formula: ⌈16/4⌉ × (5,000 + 5,000) = 40,000.
- Fee for the selected topic specification: The topic specification specifies the maximum number of topics that you can create on the Enterprise Platinum Edition instance.
- Fee for the selected storage specification: The storage specification specifies the size of the exclusive physical storage space for the Enterprise Platinum Edition instance.
Billing details
For information about the pricing and related examples of Enterprise Platinum Edition instances, visit the buy page of Enterprise Platinum Edition instances.