This topic describes the billable items and billing methods of Message Queue for Apache Kafka to help you properly purchase resources and choose an appropriate billing method.

Billable items

The following table describes the billable items of Message Queue for Apache Kafka.

Billable item Description
Internet traffic Internet traffic is divided into read traffic and write traffic. The maximum read traffic and maximum write traffic provided by Message Queue for Apache Kafka are the same. Select a bandwidth based on your peak read or write traffic, whichever is higher. This billable item applies only to instances that allow connections over the Internet and virtual private clouds (VPCs).
Traffic specification
  • The traffic specification refers to all the traffic consumed by your elastic network interfaces (ENIs). The traffic includes both business traffic and in-cluster replication traffic. Business traffic is the actual messaging traffic of your business. In-cluster replication traffic is the traffic generated when the data in your Message Queue for Apache Kafka cluster is backed up multiple times. By default, the cluster has a total of three replicas after a backup.
  • Business traffic is divided into read traffic and write traffic. The ratio of maximum read traffic to maximum write traffic is 1:1 for Professional Edition (High Write) and is 5:1 for Professional Edition (High Read). Select an ENI traffic specification based on your peak read or write traffic, whichever is higher. To ensure business stability, we recommend that you purchase a margin for buffering. The margin is about 30% of your peak read or write traffic, whichever is higher.
Disk capacity
  • In consideration of performance and storage space, the minimum disk capacity varies based on the traffic specification.
  • Message Queue for Apache Kafka supports ultra disks and solid-state drives (SSDs). We recommend that you use SSDs.
  • The price of a disk varies with the disk type.
  • Exercise caution when you select a disk type, because 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 Professional 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 300 GB. An additional 600 GB of storage space is free for you to store backups.
      Notice Free storage space applies only to topics whose storage engines are cloud storage. For more information about cloud storage, see Storage engine comparison.
Topic quota
  • The maximum number of topics or partitions allowed varies with your traffic specification.
  • In addition to the default number of partitions, 16 additional partitions are available each time you purchase a topic. For example, you have purchased an instance that has 50 topics, a maximum traffic rate of 20 Mbit/s, and 400 default partitions. After you purchase another 10 topics for this instance, 160 additional partitions are available for the instance. The total number of partitions allowed increases 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 has 50 topics, the number of topics that you can create in the instance is 100.
Note
  • You are charged for the items that are described in the previous tables.
  • You can adjust the value of the Maximum Message Retention parameter to save disk space. This parameter specifies the maximum period for which messages can be retained when disk space is sufficient. If disk usage reaches 85%, the disk capacity is insufficient. In this case, the system deletes messages from the earliest stored ones to ensure service availability. By default, messages are retained for a maximum of 72 hours. You can also select a period between 24 hours and 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 method

Message Queue for Apache Kafka supports only the subscription billing method.

Related topics

  • Topics about subscription
    Billing rules
    Overdue payments
    Instance renewal
  • Other related topics
    Set the notification policy for imminent overdue payments and instance release
    View billing and usage details
    FAQ