:Billing for legacy Serverless Standard and Professional Edition instances

Billing formula

Fees for API calls = Total number of API calls × Unit price per call (USD/call)

Message send/receive count calculation rules

Message Send and Receive Count = Message Receive Count + Message Delivery Count.

• Number of received messages: The number of messages that the server receives from producers. For example, if a topic receives five messages, the number of received messages is five.

• Number of delivered messages: The number of times the server delivers messages to consumers. Each successful delivery of a message is counted as one delivery, regardless of whether the message is processed or an ACK response is returned.

• Payload size: The number of API calls for billing is calculated based on the message size. The base unit for calculation is 4 KB. The size of a message smaller than 4 KB is rounded up to 4 KB. For example, if you deliver an 18 KB message, the number of deliveries is calculated as ⌈18/4⌉ = 5.

  Note

  ⌈ ⌉ indicates rounding up to the nearest integer.

Tiered pricing rules

• The unit price for messages sent and received by Serverless instances is based on a tiered billing model. The pricing tiers are determined by the total monthly message volume of an instance. Messages in each tier are charged at the unit price for that tier.

• When calculating the cumulative number of calls for a tier, calls for different message types, and calls for sending and subscribing to messages, are accumulated separately.

  For example, the number of calls for sending normal messages and the number of calls for subscribing to normal messages are not added together.

• Sending normal messages refers to producers sending normal messages. Sending advanced messages refers to producers sending scheduled and delayed messages, ordered messages, or transactional messages.

• In ApsaraMQ for RocketMQ, messages can be delivered concurrently or sequentially. You can select a delivery method when you create a group. The unit prices for different delivery methods vary.

Tiered unit prices

The unit prices of API calls for Serverless instances vary by region. The following tables list the prices.

Billing example

This example is for a Serverless ApsaraMQ for RocketMQ Standard Edition instance in the China (Hangzhou) region. Assume the instance has the following hourly usage:

• 100 million normal messages are sent.

• 200 million normal messages are subscribed to.

• No advanced messages are sent or subscribed to.

The billing for sent and subscribed messages for this instance is as follows:

Billing formula

Hourly storage fees = Storage space used (GB) × Unit price for storage (USD/GB/hour)

Unit price

Billing formula

Hourly topic fees = Number of topics created in the instance × Unit price per topic (USD/topic/hour)

The number of topics is calculated based on the peak number of topics in an instance within a specific hour.

For example, if you create 50 topics and then delete 20 of them within one minute, you are charged for 50 topics for that hour.

Unit price

The unit price per topic is tiered based on the number of topics.

Billing example

The following table shows the number of topics created and the corresponding fees for a Serverless ApsaraMQ for RocketMQ Standard Edition instance over a two-hour period.

Billing formula

Hourly public network fees = Total outbound traffic over the public network (GB) × Unit price for traffic (USD/GB)

Unit price

Rules for calculating message traces

The number of message traces is calculated using the following formula: Number of messages that the server receives from producers during a billing cycle + (Number of messages that the server delivers to consumers × 2).

Billing formula

Hourly message trace fees = Number of message traces × Unit price per trace (CNY/trace)

Unit price