-
Notifications
You must be signed in to change notification settings - Fork 231
Deployment: Overview
lyx edited this page Jan 17, 2025
·
1 revision
AutoMQ is designed based on block storage and object storage, such as AWS EBS and S3. It performs exceptionally well on major Public Cloud platforms, including AWS, Azure, GCP, and Alibaba Cloud. From day one, AutoMQ has been designed to support multiple Public Cloud environments and can also run on Private Cloud deployments corresponding to various cloud providers. If your Private Cloud has already deployed any of Ceph, CubeFS, MinIO, or HDFS, AutoMQ will also perform admirably.
- 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