This topic describes the instance editions, network types, billing items, and billing methods of Message Queue for Apache Kafka for you to better understand the billing rules and select instances as needed.
Message Queue for Apache Kafka provides instances of the Professional Edition and Standard Edition by specifications. The following table compares them.
|Item||Professional Edition||Standard Edition|
||Only version 0.10.x is supported.|
|Instance type||Exclusive instances, with a dedicated physical node for each instance||Virtual instances, with some instances sharing a node|
|Message storage time||Customized based on your scenarios||Up to 7 days|
|Disaster recovery||Multi-zone deployment||Single-zone deployment|
|Performance optimization||Customized based on business scenarios||Not supported|
|Cross-region message router||Coming soon||Not supported|
|Topic||Number of available topics = Number of purchased topics x 2||Number of available topics = Number of purchased topics|
Instances of the VPC type: only provide the default endpoints and can be accessed only through VPC networks
The following table describes the Message Queue for Apache Kafka billing items.
|Peak traffic||The purchase of peak traffic is described as follows:
|Disk capacity||To ensure the performance and storage space, each peak traffic specification has a
disk space limit. That is, you need to purchase an allowed disk capacity. The peak
traffic is also limited by the disk type. Message Queue for Apache Kafka supports the following disk types:
||The disk type cannot be changed after the order is placed. Select the disk type with caution. The 3-replica mechanism is used for both cloud storage and local storage. For example, if your actual business storage capacity is 100 GB, you need to purchase 300 GB for three replicas.|
- You need to pay the fees of all billing items.
- You can set the Maximum Message Retention Period parameter to conserve disk capacity. This parameter indicates the maximum retention period of a message when the disk capacity is sufficient. When the disk capacity is insufficient (that is, the disk usage reaches 85%), the old messages are deleted in advance to ensure service availability. The maximum retention period of a message is 72 hours by default. The value ranges from 24 hours to 168 hours.
- The number of API calls is not a billing item.
Total fee = (Unit price of peak traffic + Unit price of disk capacity x Purchased disk capacity/100 + Topic unit price x Number of purchased topics) x Number of months
Billing rules include the rules for peak traffic, disk capacity, and purchased topics:
- Billing rules for peak traffic
Billing rules for peak traffic are related to the instance editions.
Table 1. Billing rules for peak traffic (Standard Edition) Peak traffic (MB/s) Number of topics Number of partitions Singapore (Singapore)(USD/month) 20 50 400 370 30 50 500 530 60 80 600 760 90 100 800 960 120 150 900 1160 Table 2. Billing rules for peak traffic (Professional Edition) Peak traffic (MB/s) Number of topics Number of partitions Singapore (Singapore)(USD/month) 20 50 1100 870 30 50 1200 1040 60 80 1400 1510 90 100 1600 1920 120 150 1800 2330 160 180 2000 2740 200 200 2200 3970 250 250 2500 4570 300 300 3000 5170 600 450 4500 7030 800 500 5000 8280 1000 600 6000 9670 1200 700 7000 10780 1500 800 8000 12640 1800 900 9000 14520 2000 1000 10000 16060Note If you need a larger specification, submit a ticket.
- Billing rules for the disk capacity
Disk type Disk size（GB） Singapore (Singapore)(USD/month) Ultra disk 100 8 SSD 100 23
- Billing rules for added topics
Billing item Number of topics Singapore (Singapore)(USD/month) Topic 1 11