All Products
Search
Document Center

ApsaraMQ for RocketMQ:Overview

Last Updated:Sep 04, 2024

ApsaraMQ for RocketMQ supports the subscription, pay-as-you-go, and serverless billing methods. The billable items and billing rules of each billing method vary. During actual usage, you can select a billing method based on your use scenario and business scale to optimize costs.

Instance editions

ApsaraMQ for RocketMQ provides the following primary and sub-category instance editions to meet requirements in different scenarios and at different scales:

  • Primary editions: Standard Edition, Professional Edition, and Enterprise Platinum Edition.

  • Sub-category editions: Standalone Edition and Cluster Edition.

For information about the differences between the editions and their use scenarios, see Instance selection.

Billing methods

ApsaraMQ for RocketMQ supports the subscription, pay-as-you-go, and serverless billing methods.

Billing method

Description

Scenario

Supported instance edition

Subscription

You can use an instance only after you pay the computing fees based on the selected computing specification and subscription duration. You are charged for other resources on the instance based on the actual usage.

This billing method is suitable for scenarios in which the amount of traffic is large and stable.

  • Standard Edition

  • Professional Edition

  • Enterprise Platinum Edition

Pay-as-you-go

Computing fees are generated based on the selected computing specification and service duration of an instance after the instance is created. A bill is generated and fees are deducted from your Alibaba Cloud account every hour. You are charged for other resources on the instance based on the actual usage.

This billing method is suitable for test and short-term activity scenarios, such as special marketing activities and end-to-end stress testing activities that require timeliness.

If you want to continue using a pay-as-you-go instance after the test or short-term activity is complete, you can change the billing method of the instance to subscription. For more information, see Change the billing method of an instance from pay-as-you-go to subscription.

  • Standard Edition

  • Professional Edition

  • Enterprise Platinum Edition

Serverless

You are charged for resources based on the actual usage. Bills are generated and fees are deducted from your Alibaba Cloud account after the billing cycle (1 hour) ends.

This billing method is suitable for scenarios in which traffic greatly fluctuates or capacity is difficult to evaluate.

  • Standard Edition

  • Professional Edition

Regions

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).

Billable items of subscription and pay-as-you-go instances

The billable items of subscription and pay-as-you-go ApsaraMQ for RocketMQ instances are the same except for computing specifications.

  • Subscription instances: An upfront payment must be made based on the computing specification and subscription duration that you select.

  • Pay-as-you-go instances: Fees are generated on an hourly basis based on the computing specification that you select immediately after you purchase an instance.

The following figure describes the billable items:

image

Billable items of serverless instances

image

Change the billing method

  • Pay-as-you-go: You can change the pay-as-you-go billing method to the subscription billing method.

    For more information, see Change the billing method of an instance from pay-as-you-go to subscription.

  • Subscription: You cannot change the subscription billing method to other billing methods.

  • Serverless: You cannot change the serverless billing method to other billing methods.

Upgrade or downgrade instance configurations

After you create an ApsaraMQ for RocketMQ instance, you can upgrade or downgrade the configurations of the instance based on your business requirements.

For more information, see Upgrade or downgrade instance configurations.

References