AutoMQ is a cloud-first alternative to Kafka by decoupling durability to S3 and EBS. 10x Cost-Effective. No Cross-AZ Traffic Cost. Autoscale in seconds. Single-digit ms latency.
🔥  Free trial of AutoMQ Business Edition    📑  Documentation    📃  AutoMQ Introduction
Watch this video to learn what is AutoMQ. ⬇️ ⬇️ ⬇️
Feature | AutoMQ | Apache Kafka | Confluent | Apache Pulsar | Redpanda | Warpstream |
---|---|---|---|---|---|---|
Apache Kafka Compatibility[1] | Native Kafka | Non-Kafka | Kafka Protocol | |||
Source Code Availability | Yes | Yes | No | Yes | Yes | No |
Stateless Broker | Yes | No | No | Yes | No | Yes |
Publisher Latency(P99) | Single-digit ms latency | > 620ms | ||||
Continuous Self-Balancing | Yes | No | Yes | Yes | Yes | Yes |
Scale in/out | In seconds | In hours/days | In hours | In hours (scale-in); In seconds (scale-out) |
In hours In seconds (Enterprise Only) |
In seconds |
Spot Instance Support | Yes | No | No | No | No | Yes |
Partition Reassignment | In seconds | In hours/days | In hours | In seconds | In hours In seconds (Enterprise Only) |
In seconds |
Component | Broker | Broker Zookeeper (Non-KRaft) |
Broker Zookeeper Bookkeeper Proxy(Optional) |
Broker | Agent MetadataServer |
|
Durability | Guaranteed by S3/EBS[2] | Guaranteed by ISR | Guaranteed by Bookkeeper | Guaranteed by Raft | Guaranteed by S3 | |
Inter-AZ Networking Fees | No | Yes | No |
[1] Apache Kafka Compatibility’s definition is coming from this blog.
[2] EBS Durability: On Azure, GCP, and Alibaba Cloud, Regional EBS replicas span multiple AZs. On AWS, ensure durability by double writing to EBS and S3 Express One Zone in different AZs.
Refer to the AutoMQ Performance White Paper to see how we achieve this.
AutoMQ adopts a Shared-Storage architecture, replacing the storage layer of Apache Kafka with a shared streaming storage library called S3Stream in a storage-compute separation manner, making the Broker completely stateless.
Compared to the classic Kafka Shared-Nothing or Tiered-Storage architectures, AutoMQ’s computing layer (Broker) is truly stateless, enabling features such as Auto-Scaling, Self-Balancing, and Partition Reassignment in Seconds that significantly reduce costs and improve efficiency.
curl https://download.automq.com/community_edition/standalone_deployment/install_run.sh | bash
The easiest way to run AutoMQ. You can experience features like Partition Reassignment in Seconds and Continuous Self-Balancing in your local machine. Learn more
There are more deployment options available:
You can join the following groups or channels to discuss or ask questions about AutoMQ:
If you’ve found a problem with AutoMQ, please open a GitHub Issues.
To contribute to AutoMQ please see Code of Conduct and Contributing Guide.
We have a list of good first issues that help you to get started, gain experience, and get familiar with our contribution process. To claim one, simply reply with ‘pick up’ in the issue and the AutoMQ maintainers will assign the issue to you. If you have any questions about the ‘good first issue’ please feel free to ask. We will do our best to clarify any doubts you may have.
The business edition of AutoMQ provides a powerful and easy-to-use control plane to help you manage clusters effortlessly. Meanwhile, the control plane is more powerful in terms of availability and observability compared to the community edition.
You can check the difference between the community and business editions here.
Watch the following video and refer to our docs to see how to deploy AutoMQ Business Edition with 2 weeks free license for PoC.
⬇️ ⬇️ ⬇️
To allow users to experience the capabilities of the AutoMQ business edition without any barriers, click here to apply for a no-obligation cluster trial, and note AutoMQ Cloud Free Trial
in the message input box. We will immediately initialize an AutoMQ Cloud control panel for you soon in the cloud and give you the address of the control panel. Then, you can use the control panel to create a AutoMQ cluster or perform operations like scale in/out.
No need to bind a credit card, no cost at all. We look forward to receiving valuable feedback from you to make our product better. If you want to proceed with a formal POC, you can also contact us through Contact Us. We will further support your official POC.
Here are some of the users who have deployed AutoMQ in their production environments.
AutoMQ is a fork of the open-source Apache Kafka. Based on the Apache Kafka codebase, we found an aspect at the LogSegment level, and replaced Kafka’s storage layer with our self-developed cloud-first stream storage engine, S3Stream. This engine can provide customers with high-performance, low-cost, and unlimited stream storage capabilities based on cloud storage like EBS WAL and S3. As such, AutoMQ completely retains the code of Kafka’s computing layer and is 100% fully compatible with Apache Kafka. We appreciate the work done by the Apache Kafka community and will continue to embrace the Kafka community.
Want to learn more, Talk with our product experts.