automq

AutoMQ is a cloud-native alternative to Kafka by decoupling durability to cloud storage services like S3. 10x Cost-Effective. No Cross-AZ Traffic Cost. Autoscale in seconds. Single-digit ms latency. Multi-AZ Availability.

AutoMQ
4875
335
Java

AutoMQ: A cloud-native alternative of Kafka by decoupling durability to cloud storage services like S3

👥 Big Companies Worldwide are Using AutoMQ

Here are some of our customers who are using AutoMQ from all over the world.
image

🗞️ Newest Feature

Table Topic feature for unified stream and data analysis, which now supports the S3 table feature announced at the 2024 re:Invent. Learn more.
image

🍵 AutoMQ vs Other Streaming Platforms

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 cloud storage services[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] AutoMQ’s flexible architecture can utilize the durability of various cloud storage services like S3, Regional EBS, and EFS, all offering multi-AZ durability.

🔶 Why AutoMQ

  • Cost effective: The first true cloud-native streaming storage system, designed for optimal cost and efficiency on the cloud. Refer to this report to see how we cut Apache Kafka billing by 90% on the cloud.
  • High Reliability: Leverage cloud-shared storage services to achieve zero RPO, RTO in seconds and 99.999999999% durability.
  • Serverless:
    • Auto Scaling: Monitor cluster metrics and automatically scale in/out to align with your workload, enabling a pay-as-you-go model.
    • Scaling in seconds: The computing layer (broker) is stateless and can scale in/out within seconds, making AutoMQ a truly serverless solution.
    • Infinite scalable: Utilize cloud object storage as the primary storage solution, eliminating concerns about storage capacity.
  • Manage-less: The built-in auto-balancer component automatically schedules partitions and network traffic between brokers, eliminating manual partition reassignment.
  • High performance:
    • Low latency: Accelerate writing with high-performance EBS as WAL, achieving single-digit millisecond latency.
    • High throughput: Leverage pre-fetching, batch processing, and parallel technologies to maximize the capabilities of cloud object storage.

    Refer to the AutoMQ Performance White Paper to see how we achieve this.

  • A superior alternative to Apache Kafka: 100% compatible with Apache Kafka and does not lose any key features, but cheaper and better.

✨Architecture

image

AutoMQ’s Shared Storage architecture revolutionizes the storage layer of Apache Kafka by offloading data to cloud storage, thereby rendering the Broker stateless. This architecture incorporates both WAL (Write-Ahead Logging) storage and object storage, storing all data in object storage in near real-time.

In this setup:

  • Object storage is the primary data repository, providing a flexible, cost-effective, and scalable storage solution.
  • AutoMQ introduces a WAL storage layer to counter the high latency and low IOPS associated with Object storage, thereby improving data write efficiency and lowering IOPS usage.
  • The WAL storage layer is adaptable, allowing for the selection of various storage services across different cloud providers to cater to diverse durability and performance needs. Azure Zone-redundant Disk, GCP Regional Persistent Disk, and Alibaba Cloud Regional ESSD are ideal for ensuring multi-AZ durability. For cost-effective solutions on AWS with relaxed latency scenarios, S3 can serve as WAL. Additionally, AWS EFS/FSx can balance latency and cost for critical workloads when used as WAL.

AutoMQ has developed a shared streaming storage library, S3Stream, which encapsulates these storage modules. By replacing the native Apache Kafka® Log storage with S3Stream, the entire Broker node becomes entirely stateless. This transformation significantly streamlines operations such as second-level partition reassignment, automatic scaling, and traffic self-balancing. To facilitate this, AutoMQ has integrated Controller components like Auto Scaling and Auto Balancing within its kernel, which oversee cluster scaling operations and traffic rebalancing, respectively. Please refer to here for more architecture details.

⛄ Get started with AutoMQ

Deploy Locally on a Single Host

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:

💬 Community

You can join the following groups or channels to discuss or ask questions about AutoMQ:

👥 How to contribute

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.

👍 AutoMQ Business Edition

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.

⬇️ ⬇️ ⬇️

Deploy AutoMQ Business Edition with Terraform

Free trial of AutoMQ Business Edition

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.

🐱 The relationship with Apache Kafka

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-native 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.

🙋 Contact Us

Want to learn more, Talk with our product experts.