For the subscription billing method, you can use resources only after you purchase the resources. In most cases, this billing method is suitable for stable and long-term business scenarios. Before you use the subscription billing method, you must estimate the number of resources required for your business scale. You can subscribe to the required resources for a month, multiple months, or multiple years. You must pay the subscription fee in a one-off manner. After you place an order and complete the payment, the system allocates resources to your account. If you do not renew a resource after the resource expires, the resource is reclaimed by the system.

Billable items

The following table describes the billable items of Message Queue for Apache Kafka instances that are billed based on the subscription billing method.

Billable item Description
Internet traffic Internet traffic is divided into read traffic and write traffic. The maximum read traffic and the maximum write traffic that are supported by Message Queue for Apache Kafka are the same. When you purchase an instance, compare the peak value of read traffic with the peak value of write traffic to obtain the higher value. Then, select a bandwidth based on the higher value. You are charged for this billable item only for Internet- and VPC-connected instances.
Traffic specification
  • The traffic specification refers to the computing and processing capabilities of a cluster in Message Queue for Apache Kafka. The capabilities are measured by the amount of traffic that is consumed by elastic network interfaces (ENIs). The ENI traffic is calculated based on the following formula: ENI traffic = Business traffic + Replication traffic in the cluster. Business traffic is the actual messaging traffic that is generated in your business scenarios. Replication traffic in the cluster refers to the amount of traffic that is generated when the data in your Message Queue for Apache Kafka cluster is backed up. By default, the cluster has a total of three replicas after a backup is performed.
  • Business traffic is divided into read traffic and write traffic. The ratio of the maximum read traffic to the maximum write traffic is 1:1 for Professional Edition (High Write) instances and Standard Edition (High Write) instances and 5:1 for Professional Edition (High Read) instances. When you purchase an instance, compare the peak value of read traffic with the peak value of write traffic to obtain the higher value. Then, select a traffic specification based on the higher value. To ensure business stability, we recommend that you purchase a quota that is approximately 130% of your peak read or write traffic. The excess traffic is used for buffering.
Disk capacity
  • The minimum disk capacity varies based on the traffic specification. This helps ensure high performance and cost-effective storage.
  • Message Queue for Apache Kafka supports ultra disks and SSDs. We recommend that you use SSDs.
  • The price of a disk varies based on the disk type.
  • Exercise caution when you select a disk type. The disk type cannot be changed after the order is placed.
  • By default, data is stored in three replicas.
    • For a Standard Edition instance, if you purchase a disk of 300 GB in size, the actual storage space that you can use to store your business data is 100 GB. The remaining 200 GB is used to store backups.
    • For a Profession Edition instance, if data is stored in three replicas, the disk cost is approximately 60% lower than the disk cost of a self-managed Apache Kafka instance. If you purchase a disk of 300 GB in size, the actual storage space that you can use to store your business data is 300 GB. An additional 600 GB of storage space is provided for you free of charge to store backups.
      Notice Free storage space is available only for topics that use cloud storage as the storage engine. For more information about cloud storage, see Storage engine comparison.
Quota for the number of topics
Note If you create 1,000 or more partitions in a self-managed open source Apache Kafka instance, the system performance degrades. Message Queue for Apache Kafka allows you to create 10,000 partitions or more in an instance. For example, if a topic consists of 16 partitions, the performance bottleneck of a self-managed open source Apache Kafka instance is reached after you create approximately 70 topics. You can use Message Queue for Apache Kafka to create more topics without compromising performance. If you want more partitions, more topics are required and more underlying resources must be provided to support the topics. As a result, additional costs are required when you create more partitions.
  • The maximum number of topics or partitions varies based on your traffic specification.
  • Each time you purchase an additional topic, the quota for the number of partitions is increased by 16. For example, you purchase an instance that contains 50 topics, supports a maximum traffic rate of 20 MB/s, and provides 400 default partitions. After you purchase 10 additional topics for the instance, 160 additional partitions are available for the instance. The quota for the number of partitions is increased to 560.
  • The number of topics that you can create in a Professional Edition instance is twice the number of topics that you purchase. For example, if you purchase a Professional Edition instance that provides 50 topics, you can create 100 topics in the instance.
Note
  • You are charged for the billable items that you use.
  • You can adjust the value of the Retain Messages For parameter to save disk space. The system deletes messages when the disk usage reaches the predetermined threshold or the retention period of the messages reaches the specified value of the Retain Messages For parameter. The Retain Messages For parameter specifies the maximum period that messages can be retained when the disk capacity is sufficient. When the disk usage reaches 85%, the system determines that the disk capacity is insufficient and deletes messages in the order in which the messages are stored to ensure service availability. The earliest stored message is the first message to be deleted. By default, messages are retained for a maximum of 72 hours. You can also select a period from 24 hours to 168 hours. For more information, see When are historical messages deleted from Message Queue for Apache Kafka?.
  • The number of API calls is not a billable item.

Billing formulas

For the subscription billing method, you are charged for the billable items, such as the traffic specification and disk capacity, that you specify when you create an instance. Billable items and their unit prices vary based on the instance type. For more information about the billable items, see Billable items.
  • Internet- and VPC-connected instances: Instances of this type can be accessed over the Internet or from virtual private clouds (VPCs).

    Total fee = (Unit price of Internet traffic + Unit price of a traffic specification + Unit price of disk capacity × Purchased disk capacity/100 + Price of a single topic × Number of additional topics) × Number of months

    Note The unit prices of Internet traffic are close to the unit prices of Elastic IP Address (EIP) traffic.
  • VPC-connected instances: Instances of this type can be accessed only from VPCs.

    Total fee = (Unit price of a traffic specification + Unit price of disk capacity × Purchased disk capacity/100 + Price of a single topic × Number of additional topics) × Number of months

Billing details

Note If the price information provided in the following tables is different from the price information provided on the buy page in the console, the information on the buy page takes precedence.
  • Billing for Internet traffic

    Internet traffic is billed based on bandwidth. The unit price of Internet traffic varies based on the region.

    Table 1. Billing rules for Internet traffic
    Region Unit price of bandwidth (USD/month)
    1 Mbps 2 Mbps 3 Mbps 4 Mbps 5 Mbps 6 Mbit/s and higher (n indicates the bandwidth value)
    China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), Indonesia (Jakarta), India (Mumbai), and Philippines (Manila) 3.6 7.2 11.1 15 19.6 19.6+(n-0.8)×12.5
    China (Qingdao) 3.3 6.5 10 13.5 17.6 17.6+(n-0.8)×11.3
    Singapore (Singapore), Germany (Frankfurt), and Malaysia (Kuala Lumpur) 3.6 7.2 10.8 14.4 18 18+(n-0.8)×12.5
    US (Silicon Valley), US (Virginia), and China (Hong Kong) 4.7 9.4 14.1 18.8 23.5 23.5+(n-0.8)×15.7
    Japan (Tokyo) 4 7.9 11.8 15.7 19.6 19.6+(n-0.8)×13.2
  • Billing for traffic specifications

    The billing rules for traffic specifications vary based on the instance edition. Standard Edition (High Write), Professional Edition (High Write), and Professional Edition (High Read) instances support different traffic specifications. The maximum traffic processed by a cluster and the number of free topics vary based on the traffic specification. The unit price of a traffic specification varies based on the region group to which your region belongs.

    For more information about the specifications of each instance edition, see Instance editions.

    • For information about the billing rules for traffic specifications of Standard Edition (High Write) instances, see Table 2.
    • For information about the billing rules for traffic specifications of Professional Edition (High Write) instances, see Table 3.
    • For information about the billing rules for traffic specifications of Professional Edition (High Read) instances, see Table 4.
    Table 2. Billing rules for traffic specifications of Standard Edition (High Write) instances
    Traffic specification Maximum read traffic of ENIs (MB/s) Maximum write traffic of ENIs (MB/s) Number of free topics Number of free partitions Unit price in region group 1 (USD/month) Unit price in region group 2 (USD/month) Unit price in region group 3 (USD/month)
    alikafka.hw.2xlarge 3×20 3×20 50 400 250 370 340
    alikafka.hw.3xlarge 3×30 3×30 50 500 360 530 480
    alikafka.hw.6xlarge 3×60 3×60 80 600 520 760 700
    alikafka.hw.9xlarge 3×90 3×90 100 800 660 960 880
    alikafka.hw.12xlarge 3×120 3×120 150 900 800 1160 1070
    Table 3. Billing rules for traffic specifications of Professional Edition (High Write) instances
    Traffic specification Maximum read traffic of ENIs (MB/s) Maximum write traffic of ENIs (MB/s) Number of free topics Number of free partitions Unit price in region group 1 (USD/month) Unit price in region group 2 (USD/month) Unit price in region group 3 (USD/month)
    alikafka.hw.2xlarge 3×20 3×20 50 1100 600 870 800
    alikafka.hw.3xlarge 3×30 3×30 50 1200 780 1040 1040
    alikafka.hw.6xlarge 3×60 3×60 80 1400 1130 1510 1510
    alikafka.hw.9xlarge 3×90 3×90 100 1600 1440 1920 1920
    alikafka.hw.12xlarge 3×120 3×120 150 1800 1750 2330 2330
    alikafka.hw.16xlarge 3×160 3×160 180 2000 2060 2740 2740
    alikafka.hw.20xlarge 3×200 3×200 200 2200 2980 3970 3970
    alikafka.hw.25xlarge 3×250 3×250 250 2500 3430 4570 4570
    alikafka.hw.30xlarge 3×300 3×300 300 3000 3880 5170 5170
    alikafka.hw.60xlarge 3×600 3×600 450 4500 5280 7030 7030
    alikafka.hw.80xlarge 3×800 3×800 500 5000 6220 8280 8280
    alikafka.hw.100xlarge 3×1000 3×1000 600 6000 7270 9670 9670
    alikafka.hw.120xlarge 3×1200 3×1200 700 7000 8100 10780 10780
    alikafka.hw.150xlarge 3×1500 3×1500 800 8000 9500 12640 12640
    alikafka.hw.180xlarge 3×1800 3×1800 900 9000 10910 14520 14520
    alikafka.hw.200xlarge 3×2000 3×2000 1000 10000 12070 16060 16060
    Table 4. Billing rules for traffic specifications of Professional Edition (High Read) instances
    Traffic specification Maximum read traffic of ENIs (MB/s) Maximum write traffic of ENIs (MB/s) Number of free topics Number of free partitions Unit price in region group 1 (USD/month) Unit price in region group 2 (USD/month) Unit price in region group 3 (USD/month)
    alikafka.hr.2xlarge 50+2×10 10+2×10 50 1100 600 870 800
    alikafka.hr.3xlarge 75+2×15 15+2×15 50 1200 780 1040 1040
    alikafka.hr.6xlarge 150+2×30 30+2×30 80 1400 1130 1510 1510
    alikafka.hr.9xlarge 180+2×45 45+2×45 100 1600 1440 1920 1920
    alikafka.hr.12xlarge 240+2×60 60+2×60 150 1800 1750 2330 2330
  • Billing for disk capacity

    The billing rules for disk capacity vary based on the disk type. The unit price of disk capacity varies based on the region group to which your region belongs. If the free disk capacity provided in the traffic specification does not meet your business requirements, you can purchase additional disk capacity by adjusting the value of the Disk Capacity parameter on the buy page to a larger value.

    Disk type Disk capacity (GB) Unit price in region group 1 (USD/month) Unit price in region group 2 (USD/month) Unit price in region group 3 (USD/month)
    Ultra disk 100 6 8 8
    SSD 100 16 23 21
    Note
    • The disk cost of a Professional Edition instance that stores data in three replicas is approximately 60% lower than the disk cost of a self-managed open source instance.
    • The minimum disk capacity is used to avoid issues such as rollback failures. Rollback failures occur when messages are not frequently deleted. If you want to reduce the minimum disk capacity in specific scenarios, submit a ticket to contact technical support.
    • If you require a larger disk capacity or a local disk, submit a ticket.
  • Billing for additional topics

    If the number of free topics that are provided in the traffic specification does not meet your business requirements, you must purchase more topics by adjusting the value of the Topics parameter on the buy page to a larger value. Each time you purchase an additional topic, the quota for the number of partitions is increased by 16. If the specified number of topics reaches the upper limit that is allowed by the current traffic specification, we recommend that you select a higher traffic specification because a higher traffic specification corresponds to more topics. This helps reduce your costs. The unit price of each additional topic varies based on the region group.

    Billable item Number of topics Unit price in region group 1 (USD/month) Unit price in region group 2 (USD/month) Unit price in region group 3 (USD/month)
    Topic 1 7 11 10
    Note The default number of topics indicates the minimum number of topics that are supported for an instance. The system still allocates resources to the instance based on the minimum number of topics even if you specify a smaller number of topics. In this case, your costs are not reduced.
  • Table 5.
    Region group Region
    Region group 1 China (Hangzhou)
    China (Shanghai)
    China (Qingdao)
    China (Beijing)
    China (Zhangjiakou)
    China (Hohhot)
    China (Ulanqab)
    China (Shenzhen)
    China (Heyuan)
    China (Guangzhou)
    China (Chengdu)
    Region group 2 China (Hong Kong)
    Singapore (Singapore)
    Japan (Tokyo)
    US (Virginia)
    US (Silicon Valley)
    Germany (Frankfurt)
    UK (London)
    Region group 3 Malaysia (Kuala Lumpur)
    India (Mumbai)
    Indonesia (Jakarta)
    Philippines (Manila)