README

Diskless Kafka® on S3, Offering 10x Cost Savings and Scaling in Seconds.



  📑&nbsp Documentation&nbsp&nbsp&nbsp
  🔥&nbsp Explore AutoMQ Playground Now&nbsp&nbsp&nbsp




![-yellow)](https://www.automq.com/blog/automq-vs-apache-kafka-a-real-aws-cloud-bill-comparison?utm_source=github_automq)
![-orange)](https://www.automq.com/docs/automq/benchmarks/automq-vs-apache-kafka-benchmarks-and-cost?utm_source=github_automq)











  
    
    
    
    
    
  
  
    
    
    
    
    
  




- From 6 Hours to Seconds: How Grab Achieved 3x Data Streaming Efficiency with AutoMQ
- Tencent Cloud EMR uses AutoMQ as a first-party service
- 2.2B Messages a Day: LG U+ Modernizes Log Pipelines with AutoMQ on AWS
- Geely: Powering Hybrid Cloud Streaming for a 10-Million-Vehicle Fleet
- Bambu Lab: Unifying Multi-Cloud Data Streaming with Stateless Kafka
- Honda: Slashing Kafka TCO by 50% with Cloud-Native Diskless Architecture
- Avia Games: Eliminating Maintenance Disruptions by Migrating from AWS MSK to AutoMQ
- Why JD.com Replaces Kafka with AutoMQ at 40 GiB/s Scale
- iQIYI: Architectural Agility for a Cloud-Native Streaming Journey
- miHoYo: Eliminating Kafka Over-Provisioning with True On-Demand Scaling
- FunPlus: Diskless Kafka Eliminates AWS Cross-AZ Traffic Costs for Real Savings
- Hungry Studio: Building a Multi-Cloud Real-Time Streaming Analytics Architecture on AutoMQ


 Prerequisites
Before running AutoMQ locally, please ensure:
- Docker version 20.x or later
- Docker Compose v2
- At least 4 GB RAM allocated to Docker
- Ports 9092 and 9000 are available on your system


 [!Tip]
 Deploying a production-ready AutoMQ cluster is challenging. This Quick Start is only for evaluating AutoMQ features and is not suitable for production use. For production deployment best practices, please contact our community for support.

The docker/docker-compose.yaml file provides a simple single-node setup for quick evaluation and development:
shell
curl -O https://raw.githubusercontent.com/AutoMQ/automq/refs/tags/1.5.5/docker/docker-compose.yaml && docker compose -f docker-compose.yaml up -d

This setup features a single AutoMQ node serving as both controller and broker, alongside MinIO for S3 storage. All services operate within a Docker bridge network called automq_net, allowing you to start a Kafka producer in this network to test AutoMQ:
shell
docker run --network automq_net automqinc/automq:latest /bin/bash -c \
"/opt/automq/kafka/bin/kafka-producer-perf-test.sh --topic test-topic --num-records=1024000 --throughput 5120 --record-size 1024 \
--producer-props bootstrap.servers=server1:9092 linger.ms=100 batch.size=524288 buffer.memory=134217728 max.request.size=67108864"

After testing, you can destroy the setup with:
shell
docker compose -f docker-compose.yaml down

The docker/docker-compose-cluster.yaml file offers a more complex setup with three AutoMQ nodes, ideal for testing AutoMQ's cluster features, and can be run in the same way.

There are more deployme