ApsaraMQ for RocketMQ:Billing of serverless instances

• Serverless ApsaraMQ for RocketMQ instances are available only in the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), China (Chengdu), Singapore, Germany (Frankfurt), and US (Virginia).

• If you access a serverless ApsaraMQ for RocketMQ instance over the Internet, you must set additional configuration items in the SDK code. For more information, see Version description for accessing serverless instances over the Internet.

Billable items

Messaging fees

You are charged messaging fees for a serverless ApsaraMQ for RocketMQ instance based on the total number of API calls that are initiated to receive and deliver messages.

Billing formula

Messaging fees = Total number of API calls initiated to receive and deliver messages × Unit price of API calls (USD per API call)

Rules for calculating the number of API calls initiated to receive and deliver messages

Number of API calls initiated to receive and deliver messages = Number of API calls initiated to receive messages + Number of API calls initiated to deliver messages

• Number of API calls initiated to receive messages: the number of messages that the broker receives from producers. For example, if a topic receives five messages, the number of API calls initiated to receive messages is 5.

• Number of API calls initiated to deliver messages: the number of times the broker delivers messages to consumers. Each successful delivery is counted as one API call initiated to deliver a message, regardless of whether the message is processed and whether an acknowledgment (ACK) is returned.

• Payload size: When you calculate the number of API calls that are initiated to deliver a message, you must use a payload multiplier that is calculated based on a message size of 4 KB. If the size of a message is not divisible by 4, the value is rounded up to the next smallest integer. For example, if you deliver a message whose size is 18 KB, the number of API calls that are initiated to deliver the message is 5. The number of API calls is calculated by using the following formula: ⌈18/4⌉ = 5.

  Note

  ⌈ ⌉ indicates that the value is rounded up to the next smallest integer.

Tiered pricing rules

• The unit prices of API calls initiated to receive and deliver messages in serverless ApsaraMQ for RocketMQ instances are divided into different tiers based on the monthly total number.

• When calculating the total number of API calls initiated to receive and deliver messages in a serverless instance, you must separately count the API calls of different types of messages and use different price tiers for message receipt and delivery.

  For example, you cannot use the total number of API calls initiated to deliver and receive normal messages as the criterion to determine the price tier.

• The number of API calls initiated to deliver normal messages is the number of normal messages that are sent by producers. The number of API calls initiated to deliver featured messages is the number of scheduled and delayed messages, ordered messages or transactional messages that are sent by producers.

• Message delivery in ApsaraMQ for RocketMQ can be divided into concurrent delivery and ordered delivery. You can select a delivery method when you create a group. The unit prices for message delivery vary based on the delivery method.

Prices at different tiers

The unit prices of API calls initiated to receive and deliver messages in serverless ApsaraMQ for RocketMQ instances vary based on the region. The following tables describe the unit prices.

Billing example

A serverless ApsaraMQ for RocketMQ Standard Edition instance in the China (Hangzhou) region is used to deliver and receive messages. The number of API calls that are initiated to receive and deliver messages is the same each hour. The following items describe the details:

• 100 million API calls are initiated to deliver normal messages each hour.

• 200 million API calls are initiated to receive normal messages each hour.

• No API calls are initiated to receive or deliver featured messages.

The following table describes the messaging fees of the instance.

Storage fees

You are charged storage fees for storage space in serverless ApsaraMQ for RocketMQ instances based on the storage size and duration. A storage duration less than 1 hour is rounded up to 1 hour.

Billing formula

Storage fees per hour = Storage space (GB) × Unit price of storage (USD per GB-hour)

Unit prices

Topic fees

You are charged topic fees for topics on serverless ApsaraMQ for RocketMQ instances based on the number of topics.

Billing formula

Topic fees per hour = Number of topics created on the instance × Unit price of topics (USD per topic-hour)

When you calculate the topic fees of an instance, use the highest number of topics reached during the hour.

For example, if you create 50 topics and then delete 20 topics within an hour, 50 is used as the number of topics to calculate topic fees.

Unit prices

The unit prices of topics vary based on the number of topics.

Billing example

A serverless ApsaraMQ for RocketMQ Standard Edition instance is used to receive and deliver messages. The following table describes the number of topics created on the instance and the topic fees over a period of two hours.

Internal network traffic fees

You can access serverless ApsaraMQ for RocketMQ instances in virtual private clouds (VPCs). In this case, you are charged internal network traffic fees.

Internal network traffic fees are billed to PrivateLink instead of ApsaraMQ for RocketMQ.

For more information, see Billing.

Internet traffic fees

When you access a serverless ApsaraMQ for RocketMQ instance over the Internet, you are charged fees for outbound Internet traffic.

If the Internet access feature is not enabled, you are not charged Internet traffic fees.

Message trace fees

After you enable the message trace feature for a serverless ApsaraMQ for RocketMQ instance, you are charged message trace fees based on the number of message traces.

Rule for calculating message trace fees

The number of message traces in a billing cycle is equal to the total number of messages that are delivered and received on the broker in the billing cycle.

Billing formula

Message trace fees per hour = Number of message traces × Unit price of message traces (USD per message trace)

Unit prices