ApsaraMQ for Kafka is a fully managed distributed message queue service, fully compatible with Apache Kafka 0.10.x to 3.x. Migrate from self-managed Kafka clusters without code modification.
At a glance
Attribute | Details |
Kafka compatibility | Apache Kafka 0.10.x to 3.x, all standard clients supported |
Max write throughput | Up to 50 GB/s |
Partition scalability | Tens of thousands of partitions with no performance degradation |
Scaling speed | Seconds |
Service availability | 99.99% |
Data reliability | 99.9999999% (nine 9s) |
Billing | Pay-as-you-go (Serverless instances) |
Full Apache Kafka compatibility
ApsaraMQ for Kafka supports Apache Kafka versions 0.10.x to 3.x. Connect with any standard Apache Kafka client -- no proprietary SDK required.
Existing producers, consumers, and Kafka Connect pipelines work as-is. Migrate workloads built on the open source Apache Kafka ecosystem without code modification.
Managed operations and observability
A dedicated operations team and automated tooling handle cluster health, so you can focus on building applications.
HouseKeeping diagnostics: Checks the status of core links, scans and diagnoses clusters at one-minute intervals, generates alerts for unhealthy instances, and produces daily inspection reports. For more information, see Inspection description.
NoteIf an unhealthy instance is detected during a health inspection, the risk items are displayed on the Instance Risks tab of the Instance Details page.
Consumer group monitoring: Tracks message accumulation across consumer groups and alerts on anomalies, so issues surface before they affect downstream systems.
Full API coverage: Manage resources and automate operations programmatically through a complete set of API operations.
Elastic traffic (Serverless): Serverless ApsaraMQ for Kafka instances scale traffic automatically, eliminating the need to provision for peak capacity.
Performance
The ApsaraMQ for Kafka kernel resolves a key limitation of open source Apache Kafka: performance degradation at high partition counts. Where open source Kafka slows down at thousands of partitions, the optimized kernel sustains full throughput across tens of thousands of partitions.
Metric | Capability |
Write throughput | Up to 50 GB/s |
Partition scale | Tens of thousands of partitions, no performance loss |
Scaling speed | Seconds |
Topic concurrency | Tens of thousands of topics with concurrent reads and writes |
Availability and data durability
Metric | SLA |
Service availability | 99.99% |
Data reliability | 99.9999999% (nine 9s) |
Persistent message storage: Messages are persistently enqueued, providing high data reliability and service availability.
Sustained throughput under backlog: Cluster throughput remains stable even when large volumes of messages accumulate.
Stable performance during rolling updates: Write performance is maintained during phased updates, service upgrades, and cold data reads.
Data ecosystem integration
ApsaraMQ for Kafka connects to Alibaba Cloud services and the broader big data ecosystem:
Connectors: Connect to Alibaba Cloud services and third-party systems for data integration and real-time computing.
Built-in ETL: Fully managed extract, transform, and load (ETL) components with programmable functions for flexible data processing -- no separate ETL infrastructure required.
Security
Dimension | Capabilities |
Authentication | Simple Authentication and Security Layer (SASL) identity verification, integrated with the Alibaba Cloud account system |
Authorization | Alibaba Cloud accounts, Resource Access Management (RAM) users, Security Token Service (STS), blacklists, and whitelists |
Encryption | SSL-encrypted connections to prevent interception or tampering during transmission |
Network isolation | Virtual Private Cloud (VPC) access and internet access; configure CIDR blocks, route tables, and gateways; deploy alongside Elastic Compute Service (ECS), ApsaraDB RDS, and Server Load Balancer (SLB) instances |
Cost efficiency
Serverless ApsaraMQ for Kafka instances use pay-as-you-go billing -- charges are based on actual usage, so there is no cost for idle capacity.
Comparison with open source Apache Kafka
ApsaraMQ for Kafka extends open source Apache Kafka with managed operations, higher partition scalability, and reliable storage. For a detailed comparison, see Comparison between ApsaraMQ for Kafka and open source Apache Kafka.
Dimension | Open source Apache Kafka | ApsaraMQ for Kafka |
Operations | Self-managed cluster provisioning, patching, and monitoring | Fully managed with HouseKeeping diagnostics, automated alerting, and API-driven operations |
Partition scale | Performance degrades at thousands of partitions | Tens of thousands of partitions with no performance loss |
Scaling | Manual broker addition and partition rebalancing | Scales in seconds |
Availability | Depends on your operational maturity | 99.99% service availability SLA |
Data reliability | Depends on replication configuration | 99.9999999% (nine 9s) |
Write throughput | Limited by cluster size and tuning | Up to 50 GB/s |
Security | ACLs, limited authentication options | SASL, SSL, RAM, STS, VPC network isolation |