Spotinst Radius provides availability, durability and cost-efficiency for DB instances using Amazon RDS
Helping corporations to grow with confidence on top of AWS
When you provision an Amazon RDS instance, Spotinst Radius creates a standby instance and synchronously replicates the primary DB data to a different Availability Zone. In case of an instance failure (AWS hardware or storage failure), Radius performs an automatic fail-over to the standby instance so that you can resume database operations immediately.
Multi-AZ Deployments Using Spot Instances
Run your standby DB Instances on Spot and save up to 90% of your RDS & EC2 costs. Instead of running both your Primary and Standby RDS Instances using On-Demand pricing, Spotinst Radius enables you to run your Slave Instances on Spot by creating a standby instance and synchronously replicates the primary DB data to a different Availability Zone. In case of an instance failure (AWS hardware or storage failure), Radius performs an automatic fail-over to the standby instance so that you can resume database operations immediately.
Read-Replicas Using Spot Instances
Radius for MySQL and Postgres SQL allows to use built-in replication called “Read Replicas” to scale beyond the capacity constraints of a single DB instance. Read-heavy database workloads are perfect fit to achieve enhanced performance using read replicas. It is also a no-brainer to run those Read Replicas servers on EC2 Spot Instances to dramatically reduce costs while increasing performance.
Unlike single-AZ RDS deployments, where your I/O actually is suspended, Radius takes backup from the standby server.
Radius detects and automatically recovers from the most common failure scenarios:
Loss of heartbeat in primary database
Loss of network connectivity
Manual user request for fail-over
Provision a Single AZ RDS DB Instance using the AWS management console
Provision a Standby Instance using Spotinst Radius
Get a database endpoint from Radius
Upon fail-over, Radius will perform a fail-over automatically to the Spot Standby DB Instance
After a successful fail-over, Radius will revert back to an On-Demand Instance to maintain high availability
Radius keeps your DB endpoint the same so your applications can resume database operations without the need for manual intervention. Upon successful fail-over, Radius tries to fall over again back to your primary database server so that your environment will keep running on on-demand/reserved instances as the primary, while the standby instance will run on EC2 Spot Instance.