Share the cloud-native technologies currently employed or planned by AutoMQ(https://t.co/rebz0ginZi): 1. Spot Instances(https://t.co/TdP6MLlAIz): Offload storage to EBS and S3, and make the broker stateless to leverage Spot Instances for up to 90% cost savings. 2.

1 min read Original article ↗

Share the cloud-native technologies currently employed or planned by AutoMQ(github.com/AutoMQ/automq): 1. Spot Instances(aws.amazon.com/ec2/spot/): Offload storage to EBS and S3, and make the broker stateless to leverage Spot Instances for up to 90% cost savings. 2. ASG(aws.amazon.com/autoscaling/): The lightweight Kubernetes provided by the IaaS layer is simple yet powerful for achieving auto-scaling. 3. EBS & Multi-Attach(docs.aws.amazon.com/ebs/latest/use…): EBS ensures data durability with 3 replicas, freeing AutoMQ from managing replication. Each broker relies on a single EBS volume for WAL, with Multi-Attach ensuring resilience against instance failures. 4. NVMe Reservations(aws.amazon.com/blogs/aws/new-…): Addressing shared storage challenges is simpler with NVMe Reservations, which offer a straightforward way to implement Fencing. 5. Regional EBS(cloud.google.com/compute/docs/d…): Contrary to common belief, EBS can handle AZ-level failures, thanks to Regional EBS—a feature also available in both Azure and GCP. 6. S3 Express One Zone(aws.amazon.com/s3/storage-cla…): This addition to the object storage family, when combined with EBS, allows AutoMQ to provide Regional WAL, filling a gap left by AWS's lack of Regional EBS. 7. S3: Obviously, we all need it. Do you know any other products that use the above technologies?