All Products
Search
Document Center

Elastic Compute Service:Deploy a high-availability architecture

Last Updated:Jan 31, 2024

High-availability architectures provide features such as service distribution, scalability, and multi-zone deployment. Compared with an Elastic Compute Service (ECS) instance, a high-availability architecture is more stable and scalable when databases and applications are deployed.

Benefits

A high-availability architecture provides the following benefits:

  • A high-availability multi-zone Classic Load Balancer (CLB) instance is used to distribute traffic to multiple ECS instances to increase the throughput of applications, eliminate single points of failure, and improve the availability of applications. The CLB instance allows automatic multi-zone deployment and enhances disaster recovery capabilities.

  • You can use custom images to create identical ECS instances and then add the instances to the backend server group of the CLB instance to achieve high availability. A CLB instance supports Layer-4 and Layer-7 listeners and can use multiple algorithms at the same time, such as round robin, weighted round robin, and weighted least connections, to properly allocate computing resources to backend ECS instances.

  • ApsaraDB RDS instances are fine-tuned for high-concurrency scenarios and provide features that increase throughput and stability, such as thread pooling, parallel replication, and hidden primary keys. CloudDBA provides comprehensive performance metrics that allow you to monitor instance usage, hardware usage, and slow SQL queries in real time. CloudDBA also provides optimization suggestions to help you identify and resolve issues.

Procedure

If you created an ECS instance and deployed databases and applications on the instance, you can change your single-instance deployment to a single-zone or multi-zone high-availability architecture. This section describes how to use ECS, Elastic IP address (EIP), CLB, and ApsaraDB RDS to deploy a multi-zone high-availability architecture.

image
  1. Use a custom image to create multiple identical ECS instances in different zones. For more information, see Replicate ECS instances.

  2. Create a CLB instance and add the ECS instances from different zones to the backend server group of the CLB instance to achieve high business availability. For more information, see Configure a CLB instance.

  3. Use Data Transmission Service (DTS) to migrate a self-managed database from an ECS instance to an RDS instance. Make sure that the database is not interrupted during migration and data is automatically backed up. For more information, see Migrate self-managed databases to ApsaraDB RDS instances that run RDS High-availability Edition.