Message Queue for Apache RocketMQ supports the pay-as-you-go and subscription billing methods. This topic describes these two billing methods and their billable 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 billable items

Note The billing cycle of pay-as-you-go Message Queue for Apache RocketMQ instances is 24 hours. On the next calendar day, Alibaba Cloud charges your service use of the previous calendar day, issues a bill, and deducts the service fees from your Alibaba Cloud account balance based on the bill amount. A bill is generally issued within 8 to 10 hours after the current billing cycle ends. You can check a bill the next day after the bill is generated. For more information about how to check bills, see View spending details.

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

Charges for messaging

The charges for messaging cover API calls and topic usage.
  • API calls are billed based on a tiered pricing schedule. The charges for API calls are calculated based on the unit of 1 million calls and are accurate to two decimal places. The unit price varies with the region.

    Table 1. Unit prices for API calls
    Billing tier Number of API calls (100 million calls/month) Unit price by region (USD/1 million calls)
    China (Hong Kong), 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:
      • You are charged 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 as five times that of normal messages.

        For example, when a transactional message is sent and subscribed to once, 10 API calls are billed, including five for sending and five for subscription.

        Note Message Queue for Apache RocketMQ supports the following four types of messages: normal messages, scheduled and delayed messages, transactional messages, and ordered messages. All these messages except normal messages are advanced feature messages. For more information, see Message types.
      • 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, four 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 billable item is billed daily based on a tiered pricing schedule and the number of API calls. The unit price varies with the region.
    Table 2. Unit prices for topic usage
    Billing tier Number of API calls (100 million calls/topic/day) Unit price by region (USD/topic/day)
    China (Hong Kong), 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, both accounts are charged for service use. If you use an Alibaba Cloud account to grant RAM users permissions to use Message Queue for Apache RocketMQ, the Alibaba Cloud account is charged for service use.

Subscription billable items

Enterprise Platinum Edition instances use the subscription billing method. For more information about the billable items, see the Enterprise Platinum Edition buy page.