All Products
Search
Document Center

ApsaraMQ for RocketMQ:Billing of serverless instances

Last Updated:Oct 21, 2024

ApsaraMQ for RocketMQ supports the pay-as-you-go billing method. This billing method allows you to flexibly use resources without the need to reserve them, which helps improve resource utilization and reduce business costs.

Limits

  • 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

Billable item

Required

Billing method

Settlement cycle

Messaging fees

Yes

Pay-as-you-go

Hourly

Storage fees

Yes

Topic fees

Yes

Internal network traffic fees

Yes

Internet traffic fees

No

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

Message trace fees

No

If the message trace feature is not enabled, you are not charged message trace fees.

Price calculator for serverless ApsaraMQ for RocketMQ instances

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.

Unit prices in Alibaba Cloud regions

Standard Edition instances

Region

Billing tier

Monthly total number of API calls initiated to receive and deliver messages (in 100 million)

Number of API calls initiated to deliver normal messages (USD per 1 million calls)

Number of API calls initiated to receive normal messages (USD per 1 million calls)

Number of API calls initiated to deliver featured messages (USD per 1 million calls)

Number of API calls initiated to receive featured messages (USD per 1 million calls)

China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Ulanqab), China (Heyuan), China (Guangzhou), China (Fuzhou - Local Region), China (Nanjing - Local Region), Zhengzhou (CUCC Joint Venture), China (Hong Kong), Singapore, Australia (Sydney) Closing Down, Japan (Tokyo), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), UAE (Dubai), South Korea (Seoul), Thailand (Bangkok), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila)

First tier

(0,10]

0.15

0.06

0.77

0.31

Second tier

(10,50]

0.09

0.04

0.46

0.19

Third tier

(50,200]

0.08

0.03

0.39

0.15

Fourth tier

>200

0.06

0.02

0.31

0.12

Professional Edition instances

Region

Billing tier

Monthly total number of API calls initiated to receive and deliver messages (in 100 million)

Number of API calls initiated to deliver normal messages (USD per 1 million calls)

Number of API calls initiated to receive normal messages (USD per 1 million calls)

Number of API calls initiated to deliver featured messages (USD per 1 million calls)

Number of API calls initiated to receive featured messages (USD per 1 million calls)

China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Ulanqab), China (Heyuan), China (Guangzhou), China (Fuzhou - Local Region), China (Nanjing - Local Region), Zhengzhou (CUCC Joint Venture), China (Hong Kong), Singapore, Australia (Sydney) Closing Down, Japan (Tokyo), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), UAE (Dubai), South Korea (Seoul), Thailand (Bangkok), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila)

First tier

(0,10]

0.46

0.19

2.32

0.93

Second tier

(10,50]

0.28

0.11

1.39

0.56

Third tier

(50,200]

0.23

0.09

1.16

0.46

Fourth tier

>200

0.19

0.07

0.93

0.37

Unit prices in regions on Financial Cloud

Standard Edition instances

Region

Billing tier

Monthly total number of API calls initiated to receive and deliver messages (in 100 million)

Number of API calls initiated to deliver normal messages (USD per 1 million calls)

Number of API calls initiated to receive normal messages (USD per 1 million calls)

Number of API calls initiated to deliver featured messages (USD per 1 million calls)

Number of API calls initiated to receive featured messages (USD per 1 million calls)

  • China East 1 Finance

  • China East 2 Finance

  • China South 1 Finance

  • China North 2 Finance

First tier

(0,10]

0.29

0.12

1.47

0.59

Second tier

(10,50]

0.18

0.07

0.88

0.35

Third tier

(50,200]

0.15

0.06

0.74

0.29

Fourth tier

>200

0.12

0.05

0.59

0.24

Professional Edition instances

Region

Billing tier

Monthly total number of API calls initiated to receive and deliver messages (in 100 million)

Number of API calls initiated to deliver normal messages (USD per 1 million calls)

Number of API calls initiated to receive normal messages (USD per 1 million calls)

Number of API calls initiated to deliver featured messages (USD per 1 million calls)

Number of API calls initiated to receive featured messages (USD per 1 million calls)

  • China East 1 Finance

  • China East 2 Finance

  • China South 1 Finance

  • China North 2 Finance

First tier

(0,10]

0.88

0.35

4.41

1.76

Second tier

(10,50]

0.53

0.21

2.65

1.06

Third tier

(50,200]

0.44

0.18

2.21

0.88

Fourth tier

>200

0.35

0.14

1.76

0.71

Unit prices in regions on Alibaba Gov Cloud

Standard Edition instances

Region

Billing tier

Monthly total number of API calls initiated to receive and deliver messages (in 100 million)

Number of API calls initiated to deliver normal messages (USD per 1 million calls)

Number of API calls initiated to receive normal messages (USD per 1 million calls)

Number of API calls initiated to deliver featured messages (USD per 1 million calls)

Number of API calls initiated to receive featured messages (USD per 1 million calls)

China North 2 Ali Gov 1

First tier

(0,10]

0.31

0.12

1.55

0.62

Second tier

(10,50]

0.19

0.07

0.93

0.37

Third tier

(50,200]

0.15

0.06

0.77

0.31

Fourth tier

>200

0.12

0.05

0.62

0.25

Professional Edition instances

Region

Billing tier

Monthly total number of API calls initiated to receive and deliver messages (in 100 million)

Number of API calls initiated to deliver normal messages (USD per 1 million calls)

Number of API calls initiated to receive normal messages (USD per 1 million calls)

Number of API calls initiated to deliver featured messages (USD per 1 million calls)

Number of API calls initiated to receive featured messages (USD per 1 million calls)

China North 2 Ali Gov 1

First tier

(0,10]

0.93

0.37

4.64

1.86

Second tier

(10,50]

0.56

0.22

2.79

1.11

Third tier

(50,200]

0.46

0.19

2.32

0.93

Fourth tier

>200

0.37

0.15

1.86

0.74

Unit prices in the SAU (Riyadh - Partner Region) region

Standard Edition instances

Region

Billing tier

Monthly total number of API calls initiated to receive and deliver messages (in 100 million)

Number of API calls initiated to deliver normal messages (USD per 1 million calls)

Number of API calls initiated to receive normal messages (USD per 1 million calls)

Number of API calls initiated to deliver featured messages (USD per 1 million calls)

Number of API calls initiated to receive featured messages (USD per 1 million calls)

SAU (Riyadh - Partner Region)

First tier

(0,10]

0.19

0.07

0.93

0.37

Second tier

(10,50]

0.11

0.04

0.56

0.22

Third tier

(50,200]

0.09

0.04

0.46

0.19

Fourth tier

>200

0.07

0.03

0.37

0.15

Professional Edition instances

Region

Billing tier

Monthly total number of API calls initiated to receive and deliver messages (in 100 million)

Number of API calls initiated to deliver normal messages (USD per 1 million calls)

Number of API calls initiated to receive normal messages (USD per 1 million calls)

Number of API calls initiated to deliver featured messages (USD per 1 million calls)

Number of API calls initiated to receive featured messages (USD per 1 million calls)

SAU (Riyadh - Partner Region)

First tier

(0,10]

0.56

0.22

2.79

1.11

Second tier

(10,50]

0.33

0.13

1.67

0.67

Third tier

(50,200]

0.28

0.11

1.39

0.56

Fourth tier

>200

0.22

0.09

1.11

0.45

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.

Item

First hour

Second hour

Third hour

...

Tenth hour

Eleventh hour

Twelfth hour

...

Message delivery fee

Number of API calls initiated to deliver normal messages

100 million

100 million

100 million

...

100 million

100 million

100 million

...

Total number of API calls initiated to deliver normal messages

100 million

200 million

300 million

...

1 billion

1.1 billion

1.2 billion

...

Unit price of API calls initiated to deliver normal messages (USD per 1 million calls)

0.15 (first tier)

0.15 (first tier)

0.15 (first tier)

...

0.15 (first tier)

0.09 (second tier)

0.09 (second tier)

...

Hourly message delivery fee for normal messages (USD)

15

15

15

...

15

9

9

...

Message receipt fee

Number of API calls initiated to receive normal messages

200 million

200 million

200 million

...

200 million

200 million

200 million

...

Total number of API calls initiated to receive normal messages

200 million

400 million

600 million

...

2 billion

2.2 billion

2.4 billion

...

Unit price of API calls initiated to receive normal messages (USD per 1 million calls)

0.06 (first tier)

0.06 (first tier)

0.06 (first tier)

...

0.04 (second tier)

0.04 (second tier)

0.04 (second tier)

...

Hourly message receipt fee for normal messages (USD)

12

12

12

...

8

8

8

...

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

Region

Unit price (USD per GB-hour)

All supported regions

0.0002

Topic fees

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

Note

You are charged topic fees after you create a topic, regardless of whether messages are produced in the topic. To prevent unnecessary costs, we recommend that you delete topics that you no longer require at the earliest opportunity.

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 tier

Total number of topics

Region (all supported regions)

Unit price of topics on Standard Edition instances (USD per topic-hour)

Unit price of topics on Professional Edition instances (USD per topic-hour)

First tier

(0,10]

0.006

0.012

Second tier

(10,50]

0.003

0.006

Third tier

(50,200]

0.002

0.003

Fourth tier

>200

0.001

0.002

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.

Time

Number of created topics

Number of billed topics

Unit price

Total fees

First hour

  • Created: 30

  • Deleted: 10

  • Remaining: 20

30

  • Ten topics fall into the first tier and the unit price is 0.006 USD per topic-hour.

  • Twenty topics fall into the second tier and the unit price is 0.003 USD per topic-hour.

10 × 0.006 + 20 × 0.003 = 0.12

Second hour

Created: 50

50 + 20 = 70

  • Ten topics fall into the first tier and the unit price is 0.006 USD per topic-hour.

  • Forty topics fall into the second tier and the unit price is 0.003 USD per topic-hour.

  • Twenty topics fall into the third tier and the unit price is 0.002 USD per topic-hour.

10 × 0.006 + 40 × 0.003 + 20 × 0.002 = 0.22

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.

Billing formula

Internet fees per hour = Total amount of outbound Internet traffic (GB) × Unit price of outbound Internet traffic (USD per GB)

Unit prices

Region

Unit price of outbound Internet traffic (USD per GB-hour)

China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Ulanqab), China (Heyuan), China (Guangzhou), China (Fuzhou - Local Region), China (Nanjing - Local Region), Zhengzhou (CUCC Joint Venture), China (Hong Kong), Singapore, Australia (Sydney) Closing Down, Japan (Tokyo), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), UAE (Dubai), South Korea (Seoul), Thailand (Bangkok), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila)

0.15

China East 1 Finance, China East 2 Finance, China South 1 Finance, and China North 2 Finance

0.29

China North 2 Ali Gov 1

0.31

SAU (Riyadh - Partner Region)

0.19

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

Region

Unit price of message traces (USD per 1 million message traces)

China (Hangzhou), China (Shanghai), China (Shenzhen), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Ulanqab), China (Heyuan), China (Guangzhou), China (Fuzhou - Local Region), China (Nanjing - Local Region), Zhengzhou (CUCC Joint Venture), China (Hong Kong), Singapore, Australia (Sydney) Closing Down, Japan (Tokyo), Germany (Frankfurt), UK (London), US (Silicon Valley), US (Virginia), UAE (Dubai), South Korea (Seoul), Thailand (Bangkok), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila)

0.015

China East 1 Finance, China East 2 Finance, China South 1 Finance, and China North 2 Finance

0.029

China North 2 Ali Gov 1

0.031

SAU (Riyadh - Partner Region)

0.019