ECS Instance High Availability Domain Deployment Instructions and Guidance

<p>ECS Instance Pod Deployment Instructions &amp; Guidance</p> <p><strong>Uses highly availability domain architecture to provide enhanced availability and durability for ECS Instance</strong></p> <ul> <li>Each availability domain runs on an independent infrastructure, that is, the physical host, storage device, and network device are a single set or multiple sets. Different availability domains will not mix hardware resources. When any resource fails on one availability domain, the computing resources on the other availability domain will not be affected.</li> <li>As long as users can ensure that the same application is deployed on different availability domains when deploying ECS Instance resources, high-availability switching can be achieved at the application level, which can ensure that the application will not be affected by the underlying infrastructure failure (physical host hardware failure, storage failure or network interruption).</li> <li>The user&#39;s ECS Instance network is reachable at Layer 2 in this type of availability domain, with lower network latency and less impact on services.</li> </ul> <p><strong>Deployment Recommendations</strong></p> <ul> <li>VM1 and VM2 must be on different network segments, and VM3 and VM4 can be on the same network segment.</li> <li>For the same application component, different instances can be deployed in the available zone 1 and available zone 2 under the same node (LFA1, LFA2 as shown below).</li> <li>The inter-access between applications deployed on different nodes is inter-network segment inter-access, and is generally used in the same city, remote, dual-active or disaster recovery scenarios.</li> </ul>
Did the above content solve your problem? Yes No
Please complete information!

Call us

400-151-8800

Email us

cloud@pingan.com

Online customer service

Instant reply

Technical Support

cloud products