AWS Disaster Recovery

JUNE 23, 2021

The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. Each Region hosts a highly available, multi- Availability Zone (AZ) workload stack. I use Amazon DynamoDB for the example architecture in Figure 2. DR strategies.

Disaster Recovery 63

Disaster Recovery Activation Architecture Failover 63

AWS Disaster Recovery

JANUARY 20, 2021

Many AWS customers have internal business applications spread over multiple AWS accounts and on-premises to support different business units. Route 53 Private Hosted Zones (PHZs) and Resolver endpoints on AWS create an architecture best practice for centralized DNS in hybrid cloud environment. Architecture Overview.

Architecture 68

Architecture Failover High Availability Application 68

AWS Disaster Recovery

APRIL 27, 2021

In this blog, we talk about architecture patterns to improve system resiliency, why observability matters, and how to build a holistic observability solution. As a refresher from previous blogs, our example ecommerce company’s “Shoppers” application runs in the cloud. The monolith application is tightly coupled with the database.

Architecture 74

Architecture Resilience Application Backup 74

AWS Disaster Recovery

JANUARY 25, 2022

The Availability and Beyond whitepaper discusses the concept of static stability for improving resilience. In the simplest case, we’ve deployed an application in a primary Region and a backup Region. Amazon Route 53 Application Recovery Controller (Route 53 ARC) was built to handle this scenario.

Disaster Recovery 79

Disaster Recovery Failover Outage Application 79