-
Notifications
You must be signed in to change notification settings - Fork 381
Difference with AutoMQ Business Edition
AutoMQ usage scenarios are divided based on deployment formats as follows:
-
Self-built Community Edition: You can independently deploy and maintain the AutoMQ Community Edition in a Private Cloud environment.
-
Purchase Business Edition: Utilize the Business Edition and services provided by the AutoMQ Team to obtain technical support and operational services. The Business Edition comes in two forms:
-
AutoMQ Cloud A fully-managed cloud service version provided by the AutoMQ Team, ideal for Public Cloud environments.
-
AutoMQ Enterprise A Business Edition software tailored for Private Cloud, referred to as AutoMQ Enterprise.
-
AutoMQ Community Edition is governed by the AutoMQ BSL License, and all related feature source code can be viewed in the GitHub repository.
Note:
Any user can freely access the code and software artifacts of the AutoMQ Community Edition. Please note that providing commercial services such as message queuing and stream storage to third parties requires commercial licensing from AutoMQ Inc.
Each Community Edition source code governed by the BSL license automatically converts to the Apache V2.0 license four years after release.
"The AutoMQ Team" or "AutoMQ Inc." refers to the legal entity AutoMQ HK Limited and its subsidiaries.
The AutoMQ Business Edition is tailored for enterprise-level needs, providing fully managed operations and committed SLAs. Compared to the Community Edition, it offers significant improvements and optimizations in areas such as disaster recovery, fault tolerance, scalability, and observability. The detailed comparison is as follows:
- |
AutoMQ Community Edition |
AutoMQ Business Edition |
||
---|---|---|---|---|
Product Name |
AutoMQ |
AutoMQ Cloud |
AutoMQ Enterprise |
|
Service Model |
Free Software |
SaaS Fully Managed Service [1] |
BYOC Fully Managed Service [2] |
Paid Software[3] |
Deployment Environment |
Public Cloud or Private Cloud:
|
For Public Cloud, Supported Mainstream Cloud Providers:
|
For Private Cloud, Supported Storage Technology Stack:
|
|
Resource Ownership |
IaaS resources owned by the user |
IaaS resources owned by the AutoMQ Inc. cloud account |
IaaS resources owned by the user's cloud account |
IaaS resources owned by the user |
Data Sovereignty |
100% private, data stays within the user's subnet |
100% secure, trusted to AutoMQ Inc.'s cloud account management |
100% private, data stays within the user's VPC |
100% private, data stays within the user's subnet |
Operation method |
Self-deployment and operation |
One-click activation via cloud marketplace, official website, etc., with fully-managed service, covering the following scenarios:
|
All operations are executed by the customer, with remote technical support provided by the AutoMQ Team |
|
Payment method |
[Optional] Subscribe to Technical Consultation |
|
|
|
Cost Structure |
|
Software Service Fee (Pricing Includes Cloud Resources) |
|
|
Technical Support |
|
|
|
|
Applicable Scenarios |
|
Default option for Public Cloud customers |
Some Public Cloud customers expect to leverage IaaS discounts by keeping data within their VPC, and they accept operation and maintenance authorization. |
Applicable for financial and government enterprise customers who require complete data sovereignty and environment isolation. |
-
[1] This refers to deploying both the control plane and data plane of AutoMQ Cloud to AutoMQ Inc.'s primary account's independent VPC, and integrating with the customer's VPC through VPC PrivateLink or VPC Peering.
-
[2] This refers to deploying both the control plane and data plane of AutoMQ Cloud to the customer's primary account VPC.
-
[3] This refers to deploying both the control plane and data plane of AutoMQ Enterprise to the customer's Private Cloud, where the customer is responsible for operations and maintenance, with AutoMQ Inc. providing technical support and version upgrades.
-
[4] During the operation of the AutoMQ Server, generated logs, metrics, and diagnostic data are stored in a separate object storage bucket. Customers need to grant cross-account access to this bucket to the main account of the AutoMQ Team. The AutoMQ SaaS platform analyzes customer cluster logs and metrics in real-time, ensuring the stable operation of customer clusters backed by the AutoMQ professional development team.
-
[5] AutoMQ Server is equipped with automatic fault recovery capabilities. It monitors various performance metrics of the cluster in real-time and automatically isolates any abnormal nodes. This prevents faults from impacting applications and achieves recovery within minutes. Subsequently, engineers from the AutoMQ Team will analyze the root cause of the fault in the background.
If you need to evaluate or understand the Business Edition, please fill out the form, and our product experts will contact you shortly.
Capability Group |
Capability Items |
Community Edition |
Business Edition |
---|---|---|---|
Cloud-Native Architecture Design |
Second-Level Partition Reassignment |
✅ |
✅ |
Minute-Level Smooth Scaling |
✅ |
✅ |
|
100% Compatible with Apache Kafka® |
✅ |
✅ |
|
Self-Balancing Data |
Traffic Throughput-Based Scheduling |
✅ |
✅ |
Request Pressure-Based Scheduling |
❌ |
✅ |
|
Automated Recognition of Cold Data Reads |
❌ |
✅ |
|
Automated Detection of Slow Nodes |
❌ |
✅ |
|
Disaster Recovery |
Self-Healing for Server Crashes |
✅ |
✅ |
Proactive Self-Healing for Node Hangs |
❌ |
✅ Supports proactive scheduling, isolation, and recovery capabilities for the following fault scenarios:
|
|
Multi-AZ disaster recovery |
❌ |
✅ Enables cross-AZ scheduling recovery based on Regional EBS |
|
Object storage disaster recovery |
❌ |
✅ Supports cross-region backup for S3 with automatic switching |
|
Block storage disaster recovery |
❌ |
✅ Supports rapid hot data persistence to disaster recovery EBS |
|
Multi-cloud disaster recovery |
❌ |
✅ Supports cross-cluster routing disaster recovery, including message offset and consumption state reassignment |
|
Elasticity & Cost Optimization |
Elastic Storage |
✅ Kernel natively supports pay-as-you-go S3 |
✅ Kernel natively supports pay-as-you-go S3 |
Traffic follows elastic scaling |
❌ |
✅ |
|
Supports multiple EBS and multiple WAL |
❌ |
✅ |
|
Supports single cluster multi-Bucket read and write |
❌ |
✅ |
|
Multi-metric interactive elasticity |
❌ |
✅ Supports multi-metric interactive elasticity for CPU, memory, and network throughput, with stronger adaptability to complex stress scenarios |
|
Scheduled elastic scaling |
❌ |
✅ Ready-to-use out of the box |
|
Large-scale Spot Instances |
❌ The risk of Spot reclamation needs to be addressed |
✅Out-of-the-box solution to tailor the proportion and scale of Spot instances based on business needs |
|
GUI-Based Management |
Cluster reassignment tool |
❌ |
✅ Provides managed smooth reassignment tools |
Web Console |
❌ |
✅ Offers an out-of-the-box console
|
|
Observable |
JMX Metrics |
✅ |
✅ |
Prometheus |
❌ |
✅ Provides custom metrics store dump functionality |
|
OTLP integration |
❌ |
✅ |
|
Grafana Dashboard |
❌ |
✅ Provides out-of-the-box visualization dashboard |
|
Monitoring and Alerts |
❌ |
✅ Provides out-of-the-box monitoring and alert templates, simplifying configuration
|
|
Audit Logs |
❌ |
✅ Provides out-of-the-box event auditing features (based on AWS S3 bucket)
|
|
Integration |
Kafka Connect |
✅ |
✅ |
MirrorMaker2 |
✅ |
✅ |
|
SSO/LDAP/AD Integration |
❌ |
✅ |
|
DevOps Automation |
Kafka Admin API/CLI |
✅ |
✅ |
Kubernetes |
❌ |
✅ |
|
Terraform |
❌ |
✅ |
|
Cluster management REST APIs |
❌ |
✅ |
|
Supported Cloud providers |
AWS |
✅ |
✅ |
Azure |
❌ |
✅ |
|
Google Cloud Platform |
❌ |
✅ |
|
Alibaba Cloud |
✅ |
✅ |
|
Tencent Cloud |
✅ |
✅ |
|
Huawei Cloud |
✅ |
✅ |
|
Baidu Cloud |
✅ |
✅ |
|
Chinatelecom Cloud |
✅ |
✅ |
|
China Mobile Cloud |
✅ |
✅ |
|
Supported Storage Stack |
MinIO |
✅ |
✅ |
Ceph |
✅ |
✅ |
|
CubeFS |
✅ |
✅ |
|
HDFS |
❌ |
✅ |
|
Software Artifacts |
Binary |
✅ |
✅ |
Docker |
✅ |
✅ |
|
Cloud Machine Image |
❌ |
✅ |
|
Expert Services |
Support Channels |
Community Support |
Enterprise Ticket Service |
Expert Key Support |
❌ |
|
- What is automq: Overview
- Difference with Apache Kafka
- Difference with WarpStream
- Difference with Tiered Storage
- Compatibility with Apache Kafka
- Licensing
- Deploy Locally
- Cluster Deployment on Linux
- Cluster Deployment on Kubernetes
- Example: Produce & Consume Message
- Example: Simple Benchmark
- Example: Partition Reassignment in Seconds
- Example: Self Balancing when Cluster Nodes Change
- Example: Continuous Data Self Balancing
-
S3stream shared streaming storage
-
Technical advantage
- Deployment: Overview
- Runs on Cloud
- Runs on CEPH
- Runs on CubeFS
- Runs on MinIO
- Runs on HDFS
- Configuration
-
Data analysis
-
Object storage
-
Kafka ui
-
Observability
-
Data integration