Message Queue for Apache RocketMQ supports pay-as-you-go and subscription billing methods. This topic describes the two billing methods and their billing items.

Billing methods

Message Queue for Apache RocketMQ provides Standard Edition and Enterprise Platinum Edition instances. These two types of instances use different billing methods.

Pay-as-you-go billing items

Messaging is the billing object in the pay-as-you-go billing method. The following section describes messaging charges:

Messaging charges

The messaging charges cover API calls and topic usage.
  • API calls are billed based on a tiered pricing schedule. The API call charges are calculated based on the unit of 1 million calls and are accurate to two decimal places. The billing varies depending on regions.

    Table 1. API call charges
    Billing tier API calls (100 million calls/month) Unit price by region (USD/1 million calls)
    China (Hong Kong), Singapore (Singapore), Japan (Tokyo), and UAE (Dubai) Malaysia (Kuala Lumpur), India (Mumbai), and Indonesia (Jakarta) China (Shanghai), Australia (Sydney), US (Virginia), US (Silicon Valley), Germany (Frankfurt), and UK (London)
    First tier 0~10 0.45 0.42 0.31
    Second tier 10~50 0.41 0.38 0.28
    Third tier 50~100 0.34 0.31 0.23
    Fourth tier 100~500 0.3 0.27 0.20
    Fifth tier More than 500 0.27 0.25 0.19
    The total number of API calls is calculated based on the following formula: Total number of API calls = Number of API calls to send messages + Number of API calls to subscribe to messages + Number of long polling API calls.
    • Descriptions of the number of API calls to send and subscribe to messages:
      • Charges are incurred when you initiate an API call to send or subscribe to messages no matter whether the call is successful.
      • The number of API calls to send and subscribe to featured messages is counted based on the following multiples of normal messages.
        Table 2. Multiples for API calls for featured messages
        Message type Send messages Subscribe to messages
        Transactional messages 50 times of normal messages The same as normal messages
        Ordered messages 25 times of normal messages 25 times of normal messages
        Scheduled messages and delayed messages 25 times of normal messages The same as normal messages

        If you send a transactional message once and subscribe to it once, the number of API calls equals 50 plus 1. A total of 51 API calls are billed.

        If you send an ordered message once and subscribe to it once, the number of API calls equals 25 plus 25. A total of 50 API calls are billed.

        If you send a scheduled message or delayed message once and subscribe to it once, the number of API calls equals 25 plus 1. A total of 26 API calls are billed.

      • The maximum size of a message body is 4 MB, and the billing unit is 4 KB. For example, if you send or subscribe to a 16 KB message, 4 API calls are billed. This number is obtained based on the following formula: 16/4 = 4.
    • Descriptions of the number of long polling API calls:
      • A long polling request is an API call generated by Message Queue for Apache RocketMQ to push a message in real time. Each topic has multiple queues, and each queue generates a long polling request every 15 seconds. If a message is generated in the queue within these 15 seconds, the long polling request will not be counted. If no messages are generated in the queue within these 15 seconds, an API call is counted.
      • The number of long polling API calls for featured messages is counted in the same manner as the number of API calls for normal messages.
  • Topic usage: This billing item is billed daily based on a tiered pricing schedule and the number of API calls. The billing varies depending on regions.
    Table 3. Topic usage charges
    Billing tier API calls (100 million calls/topic/day) Unit price by region (USD/1 million calls/topic/day)
    China (Hong Kong), Singapore (Singapore), Japan (Tokyo), and UAE (Dubai) Malaysia (Kuala Lumpur), India (Mumbai), and Indonesia (Jakarta) China (Shanghai), Australia (Sydney), US (Virginia), US (Silicon Valley), Germany (Frankfurt), and UK (London)
    First tier 0~10 0.45 0.42 0.31
    Second tier 100~500 0.34 0.31 0.23
    Third tier 500~1000 0.11 0.11 0.08
    Fourth tier More than 1,000 0 0 0
    Note

    If you use an Alibaba Cloud account to grant another Alibaba Cloud account permissions to use Message Queue for Apache RocketMQ, this service is billed for both accounts. If you use an Alibaba Cloud account to grant Resource Access Management (RAM) users permissions to use Message Queue for Apache RocketMQ, all fees of this service are deducted from the Alibaba Cloud account.

Subscription billing items

Subscription: Enterprise Platinum Edition instances are billed in subscription mode. For more information about the billing items, see the Enterprise Platinum Edition buy page.