Help Center/ Well-Architected Framework/ Well-Architected Framework and Practices/ Resilience Pillar/ Reference Architecture/ Typical Deployment Architecture for E-commerce Applications (99.99% Availability)/ Single-Region Solution
Updated on 2025-05-22 GMT+08:00
View PDF
Share

Single-Region Solution

The following solution uses CCE as an example to describe the deployment architecture in a single region.

Item

Solution

Redundancy

Deploy cloud service instances in HA mode, such as ELB, CCE, DCS, Kafka, RDS, and DDS instances.

Backup

Enable automated backup for RDS and DDS databases. When a data fault occurs, the latest backup can be used to restore data, meeting availability requirements.

DR

Deploy a group of applications in two AZs separately and use bidirectional replication and active-active DR. When an AZ is faulty, service in it can be automatically recovered.

Monitoring metrics and alarms

Monitor and check site statuses and instance workloads. If a site fails or a CCE, DCS, Kafka, RDS, or DDS instance is overloaded, an alarm is reported.

Auto scaling

Use CCE clusters with auto scaling of workloads.

Change error prevention

Use canary or blue-green deployment for software updates. The deployment is automatically completed and rolled back upon a fault.

Emergency recovery

Develop an emergency handling mechanism and designate related personnel to quickly make decisions and recover services. Provide solutions to common application and database problems as well as upgrade and deployment failures. Periodically perform drills to identify problems in a timely manner.

A typical deployment architecture is as follows:

The architecture has the following features:

  • The deployment architecture is layered with stateless applications and stateful databases.
  • The application system is deployed in each of the two AZs in a region of Huawei Cloud to provide intra-city DR.
    • Access layer (external GSLB): The external GSLB is used for domain name resolution and traffic load balancing. When an AZ is faulty, service traffic load is automatically switched to another AZ.
    • Application layer (ELBs, application software, and containers): ELBs are used to detect faults and distribute loads for stateless applications, while containers enable elastic scaling.
    • Middleware layer: A DCS and a DMS for Kafka cluster are deployed in each AZ.
    • Data layer: A set of RDS databases are deployed in each AZ. DRS is used for cross-AZ bidirectional database replication and DR failover. Also, data can be automatically backed up in a scheduled manner to quickly restore in the event of data loss. OBS is deployed across AZs in HA mode. If a single AZ is faulty, services are not affected.
  • The RDS database data is automatically backed up in a scheduled manner to ensure data reliability.