This topic describes the editions, billable items, and pricing of ApsaraMQ for Confluent to help you better understand its billing. You can select a billing method for your instance based on the description of this topic.
Editions
A purchased ApsaraMQ for Confluent instance corresponds to Confluent Platform 7.8.0.
ApsaraMQ for Confluent provides two instance editions with different features and prices. The following table describes the features of the editions.
Feature | Professional Edition | Enterprise Edition |
Deployment environment | Stage and product | Stage and product |
Deployment pattern | Multi-zone deployments | Multi-zone deployments |
Schema Registry | Supported | Supported |
ksqlDB | Supported | Supported |
Connector | ||
Kafka Rest Proxy | Supported | Supported |
Cluster Linking | Source and destination | Source and destination |
Schema Linking | Supported | Supported |
User management | Built-in Lightweight Directory Access Protocol (LDAP) configurations | Built-in or custom LDAP configurations |
Authentication method | SASL_SSL | SASL_SSL |
Permission management | ACL and RBAC | ACL and RBAC |
Exactly Once semantics | Supported | Supported |
Data storage compression based on keys | Supported | Supported |
Graphical management interface | Supported | Supported |
Metrics in the Prometheus format | Supported | Supported |
Integration with Simple Log Service | Supported | Supported |
Support | Regular support | Support from Alibaba Cloud experts |
SLA | 99.9% | 99.9% |
Maximum writes | 50 MB/s per 4 CUs. 250 MB/s per instance. | 50 MB/s per 4 CUs. The limit is affected by other factors and is not guaranteed. |
Maximum reads | 150 MB/s per 4 CUs. 750 MB/s per instance. | 150 MB/s per 4 CUs. The limit is affected by other factors and is not guaranteed. |
Connections | 1,000 per 4 CUs. 10,000 per instance. | 1,000 per 4 CUs. 10,000 per instance. |
Connection frequency | 50 per second per broker. | 50 per second per broker. If you require a higher connection frequency, submit a ticket. |
Request frequency | 7,500 per second per 4 CUs. 37,500 per second per instance. | 15,000 per second per 4 CUs. The limit is affected by other factors and is not guaranteed. |
Request size | 100 MB | 100 MB |
Fetch size | 55 MB | 55 MB |
Maximum message size | 20 MB | 20 MB |
Maximum partitions | Standard: 5,000. Compact: 600. | 4,500 per 4 CUs. 100,000 per instance. |
Partition creation or deletion frequency | 5,000 per 5 minutes. | 5,000 per 5 minutes. |
Billable items
You are charged for computing and storage resources in ApsaraMQ for Confluent. The following table describes the computing and storage resources required by each component of Confluent.
One capacity unit (CU) represents a computing resource with one CPU core and 4 GB of memory.
After you purchase an ApsaraMQ for Confluent instance, you cannot request a refund for the instance. Before you place an order, make sure that the specified information is correct.
Component | Computing resource (CU) | Storage resource (GB) | Replicas | Minimum CUs | Required |
Kafka broker | 4 to 20 | 800 to 30,000 | 3 to 20 | 12 | Yes |
ZooKeeper | 2 to 20 | 100 to 30,000 | 3 | 6 | Yes |
Control Center | 8 to 20 | 300 to 30,000 | 1 | 8 | Yes |
Schema Registry | 1 to 20 | None | 2 to 3 | 2 | Yes |
Connect | 1 to 20 | None | 1 to 20 | 1 | No |
ksqlDB | 5 to 20 | 100 to 30,000 | 1 to 20 | 5 | No |
Kafka Rest Proxy | 4 to 20 | None | 2 to 20 | 8 | No |
For information about the billing formulas and unit prices of ApsaraMQ for Confluent, see Subscription.