awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
AutoMQ avatar

AutoMQ/automq-for-kafka

0
View on GitHub↗
10,026 stars·727 forks·Java·Apache-2.0·34 viewswww.automq.com↗

Automq For Kafka

AutoMQ is a cloud-native streaming platform and Kafka-compatible message broker. It implements the Kafka protocol to provide integration with existing clients and ecosystems while functioning as a message queue that persists data directly to cloud object storage.

The system decouples compute from storage, allowing processing power and storage capacity to scale independently. It utilizes a shared-log architecture and object-storage-based persistence to remove dependencies on local disks, which reduces operational costs and eliminates manual disk management.

The platform includes mechanisms for automated partition balancing and dynamic resource autoscaling to handle workload demands without downtime. It supports multi-zone high availability and utilizes availability zone-aware request routing to minimize inter-zone data transfer fees.

The system also provides capabilities for cluster data migration, unified stream and table integration, and the export of system metrics for real-time monitoring.

Features

  • Streaming Platforms - A distributed system designed for high availability and automatic scaling across multiple availability zones in cloud environments.
  • Compute-Storage Separation - Decouples compute from storage to allow processing power and storage capacity to scale independently.
  • Kafka Compatible Message Brokers - Functions as a distributed streaming platform and message broker that implements the Kafka protocol.
  • Log Object Storage - Persists message logs directly to cloud-native object storage to remove dependency on local disks.
  • Object Storage Persistence - Saves data streams to compatible cloud storage instead of local disks to eliminate manual disk management.
  • Storage-Compute Architectures - Implements an architecture that decouples compute from storage, allowing each to scale independently.
  • Autoscaling Systems - Dynamically adjusts the number of compute nodes based on real-time workload metrics without data migration.
  • Kafka-Compatible Deployments - Provides a Kafka-compatible deployment optimized for cloud object storage and compute-storage separation.
  • Queue High Availability - Distributes processing across multiple availability zones to ensure continuous service during localized cloud failures.
  • Message Queue Scaling - Automatically expands or shrinks compute resources and balances partitions to handle changing workload demands.
  • Object-Storage-Based Queues - Functions as a messaging system that persists data directly to cloud object storage instead of local disks.
  • Multi-Zone Resource Distribution - Distributes data and processing across multiple availability zones to ensure continuous service during localized failures.
  • Kafka Protocol Implementations - Implements the Kafka API to provide seamless integration with existing Kafka clients and ecosystems.
  • Shared Log Architectures - Utilizes a shared-log architecture with a remote object store as the source of truth for the distributed cluster.
  • Data Migration Services - Enables moving data from compatible clusters to new environments without causing service downtime.
  • Data Migration - Moves streaming data from existing Kafka clusters to new environments without interrupting active services.
  • Stateless Compute Scaling - Implements a stateless compute layer that scales independently of the underlying object storage.
  • Cloud Infrastructure Cost Optimization - Reduces operational expenses by eliminating local disk management and minimizing inter-zone data transfer fees.
  • Availability Zone Awareness - Directs clients to brokers within the same availability zone to eliminate cross-zone data transfer fees.
  • Partition Reassignments - Provides automated reassignment of partitions to balance network traffic and data distribution across brokers.
  • Zone-Aware Routing - Routes clients to brokers within the same availability zone to eliminate cross-zone data transfer fees.
  • Messaging - Cloud-native, serverless Kafka implementation.

Star history

Star history chart for automq/automq-for-kafkaStar history chart for automq/automq-for-kafka

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Frequently asked questions

What does automq/automq-for-kafka do?

AutoMQ is a cloud-native streaming platform and Kafka-compatible message broker. It implements the Kafka protocol to provide integration with existing clients and ecosystems while functioning as a message queue that persists data directly to cloud object storage.

What are the main features of automq/automq-for-kafka?

The main features of automq/automq-for-kafka are: Streaming Platforms, Compute-Storage Separation, Kafka Compatible Message Brokers, Log Object Storage, Object Storage Persistence, Storage-Compute Architectures, Autoscaling Systems, Kafka-Compatible Deployments.

Which projects share features with automq/automq-for-kafka?

Projects with overlapping indexed features include: automq/automq — AutoMQ is a cloud-native streaming platform and Apache Kafka distribution that implements a decoupled compute and… victoriametrics/victoriametrics — VictoriaMetrics is a high-performance, scalable time series database and observability platform designed for long-term… greptimeteam/greptimedb — GreptimeDB is a distributed, open-source time-series database built for unified observability. It stores and queries… quickwit-oss/quickwit — Quickwit is a cloud-native, distributed search engine designed for observability data such as logs, traces, and… risingwavelabs/risingwave — RisingWave is a cloud-native streaming database and real-time analytics engine that uses standard SQL to process… neondatabase/neon — Neon is a serverless PostgreSQL database platform designed with a decoupled storage and compute architecture. It…

Projects sharing features with Automq For Kafka

These projects share indexed features with Automq For Kafka. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • automq/automqAutoMQ avatar

    AutoMQ/automq

    10,027View on GitHub↗

    AutoMQ is a cloud-native streaming platform and Apache Kafka distribution that implements a decoupled compute and storage architecture. It functions as an S3-backed message queue, using object storage as the primary log repository to eliminate dependencies on local disks. The platform utilizes a stateless broker architecture to enable dynamic compute scaling and automated partition balancing. This design allows the system to adjust the number of brokers in seconds and distribute network traffic without requiring manual data migration or partition reassignment. The system provides multi-avail

    Java
    View on GitHub↗10,027
  • victoriametrics/victoriametricsVictoriaMetrics avatar

    VictoriaMetrics/VictoriaMetrics

    16,343View on GitHub↗

    VictoriaMetrics is a high-performance, scalable time series database and observability platform designed for long-term storage and analysis of metric, log, and trace data. It functions as a unified backend for monitoring ecosystems, offering full compatibility with industry-standard protocols and query languages. The system is built to handle massive data volumes through a distributed architecture that supports horizontal scaling and efficient data lifecycle management. The platform distinguishes itself through a storage engine that utilizes consistent hashing for data sharding and log-struct

    Godatabasegrafanagraphite
    View on GitHub↗16,343
  • greptimeteam/greptimedbGreptimeTeam avatar

    GreptimeTeam/greptimedb

    5,968View on GitHub↗

    GreptimeDB is a distributed, open-source time-series database built for unified observability. It stores and queries metrics, logs, and traces together in a single columnar engine, supporting both SQL and PromQL for analysis. The database is designed as a Kubernetes-native operator with a decoupled compute and storage architecture, enabling horizontal scaling and multi-region deployment. What distinguishes GreptimeDB is its role as a multi-protocol ingestion gateway, accepting data through OpenTelemetry, Prometheus Remote Write, InfluxDB, Loki, Elasticsearch, Kafka, and MQTT protocols without

    Rustanalyticscloud-nativedatabase
    View on GitHub↗5,968
  • quickwit-oss/quickwitquickwit-oss avatar

    quickwit-oss/quickwit

    11,345View on GitHub↗

    Quickwit is a cloud-native, distributed search engine designed for observability data such as logs, traces, and metrics. It functions as an observability backend that decouples compute from storage by persisting indices directly in S3-compatible cloud object stores. The system is distinguished by its compatibility with the Elasticsearch REST API, allowing it to integrate with existing clients and log shippers without reconfiguration. It also serves as an OpenTelemetry data indexer, ingesting technical data via the OpenTelemetry Protocol using gRPC and HTTP. The engine utilizes a hybrid of co

    Rustbig-datacloud-nativecloud-storage
    View on GitHub↗11,345
Compare all 30 related projects→