Uses object storage instead of local disks, pay as you go and only for useage, reducing costs to as low as one-tenth.
Spot instance
AutoMQ's storage-compute separation and stateless design enable the use of Spot instances, further reducing computing costs.
Auto-Scaling, minimize idling
Supports strategies like cron and target tracking for effective management of cyclical and unexpected workload fluctuations, ensuring optimal use of cluster resources.
Multi-cloud native arch, one-click deployment to major public cloud and private clouds
Multi-Cloud arch
AutoMQ, dependent solely on object and block storage, enables seamless one-click deployment to leading cloud providers and storage stacks like Ceph, MinIO, and CubeFS.
Support Hybrid-Cloud
Supports hybrid management of multiple public clouds and datacenters, incrementally deploying new business to the public cloud, while existing business remains on private cloud.
AKU(AutoMQ Kafka Unit): Pay for AutoMQ software services. Billing based on the peak throughput by each instance. Each 1AKU supports the following capabilities.
BytesIn/BytesOut: 20MiB/s
Requests: 800 count/s
Partitions: 1125
EC2 and S3: Pay for cloud resources to cloud provider.
Billing Cycles
Billed by hour.
SaaS
Billing Items
AKU(AutoMQ Kafka Unit): AKU are units of horizontal scaling for instances in AutoMQ cloud that provide allocated resources. Each 1AKU supports the following capabilities.
BytesIn/BytesOut: 20MiB/s
Requests: 800 count/s
Partitions: 1125
Storage: AutoMQ Cloud charges for the total data stored on a given AutoMQ instance.
Ingress and egress: AutoMQ Cloud charges you for all data transfers, including requests for produce and consume and every other type of incoming or outgoing request.