ApsaraMQ for RabbitMQ Professional Edition, Enterprise Edition, and Enterprise Platinum Edition instances use the subscription billing method. This topic describes the billable items and billing rules of these instances.
Billable items
The following items are included in the billing of ApsaraMQ for RabbitMQ Professional Edition, Enterprise Edition, and Enterprise Platinum Edition instances:
(Required) Instance specifications: You are charged based on the subscription billing method.
(Optional) Elastic TPS: You are charged based on the pay-as-you-go billing method. You are charged elastic TPS fees only after you enable the elastic TPS feature for your instance.
Calculation rules for TPS
The following items describe the billable API operations for peak TPS. For information about the description of the API operations, see Request methods.
ConnectionOpen and ChannelOpen
QueueDeclare, QueueDelete, QueueBind, and QueueUnbind
ExchangeDeclare and ExchangeDelete
ExchangeBind and ExchangeUnBind
SendMessage, BasicConsume, BasicGet, BasicAck, BasicReject, BasicNack, and BasicRecover
The number of API calls is calculated based on the following rules:
Delayed messages are a type of featured message provided by ApsaraMQ for RabbitMQ. One API call to send a delayed message is counted as five API calls to send a normal message, while one API call to receive a delayed message is still counted as one API call to send a normal message.
For example, if you send two delayed messages and receive three delayed messages within a second, the total number of API calls is 13. The number of API calls is calculated by using the following formula: 2 × 5 + 3 = 13.
When you count the number of API calls to the SendMessage operation, the actual value is the number of queues to which messages are stored after the messages are routed.
For example, if you send one message to an exchange of the Fanout type and save the message to 10 queues, the number of API calls to the SendMessage operation is counted as 10.
If a message body is smaller than 64 KB in size, one API call is counted to process the message data. If a message body is larger than 64 KB in size, one API call is counted to process each 4 KB of the excess message data.
Instance specifications
Billing rules
Billable item | Required | Supported instance edition | Free quota | Billing cycle |
Peak TPS | Yes. You are charged only when you call specific API operations. For more information, see Calculation rules for TPS. |
| None. | Monthly |
Public traffic | No. You are charged for Internet traffic only if you enable the Internet access feature. |
| None. | |
Queues | Yes. |
| A specific number of connections are provided for Enterprise Edition and Enterprise Platinum Edition instances free of charge. You can view the number of free queues for each instance edition on the buy page. | |
Maximum connections | Yes. |
| A specific number of connections are provided for Enterprise Edition and Enterprise Platinum Edition instances free of charge. You can view the number of free connections for each instance edition on the buy page. | |
Message trace retention period | No. You are charged for message trace retention only if you enable the message trace feature. |
| Enterprise Platinum Edition instances allow you to retain message traces for 15 days free of charge. | |
Message storage | Yes. | Enterprise Platinum Edition | None. |
Pricing details
For information about the pricing details of each billable item of each instance edition, see the ApsaraMQ for RabbitMQ buy page.
Elastic TPS
Billable items
A limit is imposed on the peak TPS of an ApsaraMQ for RabbitMQ instance. If your actual TPS usage exceeds the specified limit of the instance, the instance is throttled. To prevent an instance from being throttled due to bursty traffic, you can enable the elastic TPS feature for the instance. For more information, see Enable the elastic TPS feature for an instance.
After you enable the elastic TPS feature for an instance, the peak TPS of the instance can be increased within a specific range. You are charged for the TPS that exceeds the specification limit.
The maximum elastic TPS value that you can specify for each instance edition is fixed. For more information, see Unit prices.
Billing rules
Item | Description |
Billable item | You are charged for elastic TPS. Value of elastic TPS = Actual TPS usage - Peak TPS in the instance specification. For example, you purchase an instance whose specification provides a peak TPS of 5,000. If the actual TPS that you use at a specific time is 6,200. You are charged elastic TPS fees for the excess 1,200 TPS. |
Billing method | Elastic TPS is billed based on the pay-as-you-go billing method. This billing method allows you to use resources before you pay for the resources. Fees are automatically deducted from the balance of your Alibaba Cloud account. |
Billing cycle | The bill is generated every minute. |
Billing formula | Elastic TPS fee in a minute = Value of elastic TPS in the minute × Unit price of elastic TPS. |
Unit prices
Item | Professional Edition | Enterprise Edition | Enterprise Platinum Edition | |
Maximum elastic TPS | 0.5 times the specification limit. | Same as the peak TPS. An upper limit of 50,000 TPS is imposed. | Same as the peak TPS. An upper limit of 50,000 TPS is imposed. | |
Unit price of elastic TPS (USD per TPS-minute) | Other regions | 0.000072 | 0.000072 | 0.000288 |
SAU (Riyadh - Partner Region) | 0.000086 | 0.000086 | 0.000346 | |
"Other regions" in the preceding table refer to all regions supported by ApsaraMQ for RabbitMQ except for the SAU (Riyadh - Partner Region) region. For more information, see Supported regions.
The upper limit of elastic TPS for an Enterprise Edition and Enterprise Platinum Edition instance is 50,000. For example, if you purchase an Enterprise Edition instance whose specification has a peak TPS of 80,000, the maximum elastic TPS of the instance is 50,000. The total TPS of the instance is 130,000.
Billing example
You purchase a Professional Edition instance whose specification has a peak TPS of 1,000 in the China (Hangzhou) region. The following table describes the TPS usage of the instance per minute within a specific hour.
Item | 00:00:00 | 00:01:00 | 00:02:00 | 00:03:00 | ...... | 00:58:00 | 00:59:00 |
Actual peak TPS | 1,200 | 1,300 | 800 | 850 | < 1,000 | 950 | 1,100 |
Elastic TPS | 200 | 300 | 0 | 0 | 0 | 0 | 100 |
The elastic TPS fee for the instance in this hour is USD 0.0432. The fee is calculated by using the following formula: (200 + 300 +100) × 0.000072 = 0.0432.