Welcome to the third publish of a multi-part collection that addresses catastrophe restoration (DR) methods with the usage of AWS-managed companies to align with buyer necessities of efficiency, price, and compliance. In half two of this collection, we launched a DR idea that makes use of managed companies by way of a backup and restore technique with a number of Areas. The publish additionally introduces a multi-site lively/passive strategy.
The multi-site lively/passive strategy is greatest for purchasers who’ve business-critical workloads with increased availability necessities over different lively/passive environments. A warm-standby technique (as in Determine 1) is extra pricey than different lively/passive methods, however offers good safety from downtime and knowledge loss outdoors of an lively/lively (A/A) atmosphere.
Determine 1. Heat standby
Implementing the multi-site lively/passive technique
By replicating throughout a number of Availability Zones in similar Area, your workloads turn into resilient to the failure of a whole knowledge middle. Utilizing a number of Areas offers essentially the most resilient choice to deploy workloads, which safeguards in opposition to the danger of failure of a number of knowledge facilities.
Let’s discover an utility that processes cost transactions and is modernized to make the most of managed companies within the AWS Cloud, as in Determine 2.
Determine 2. Heat standby with managed companies
Let’s cowl every of the parts of this utility, in addition to how managed companies behave in a multisite…
