article thumbnail

Creating an organizational multi-Region failover strategy

AWS Disaster Recovery

This allows you to build multi-Region applications and leverage a spectrum of approaches from backup and restore to pilot light to active/active to implement your multi-Region architecture. Component-level failover Applications are made up of multiple components, including their infrastructure, code and config, data stores, and dependencies.

Failover 117
article thumbnail

The Storage Architecture Spectrum: Why “Shared-nothing” Means Nothing

Pure Storage

The Storage Architecture Spectrum: Why “Shared-nothing” Means Nothing by Pure Storage Blog This blog on the storage architecture spectrum is Part 2 of a five-part series diving into the claims of new data storage platforms. And just as important, why there is more to any product or platform than just architecture.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

How an insurance company implements disaster recovery of 3-tier applications

AWS Disaster Recovery

This design needs to keep costs at a minimum, and it needs to allow for failure detection and manual failover of resources. The solution Amazon Route53 Application Recovery Controller (Route53 ARC) helps manage and orchestrate application failover and recovery across multiple AWS Regions or on-premises environments.

article thumbnail

Implementing Multi-Region Disaster Recovery Using Event-Driven Architecture

AWS Disaster Recovery

In this blog post, we share a reference architecture that uses a multi-Region active/passive strategy to implement a hot standby strategy for disaster recovery (DR). DR implementation architecture on multi-Region active/passive workloads. Fail over with event-driven serverless architecture. This keeps RTO and RPO low.

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part I: Strategies for Recovery in the Cloud

AWS Disaster Recovery

All requests are now switched to be routed there in a process called “failover.” For tighter RTO/RPO objectives, the data is maintained live, and the infrastructure is fully or partially deployed in the recovery site before failover. Architecture of the DR strategies. Backup and restore DR architecture. Pilot light.

article thumbnail

Using Route 53 Private Hosted Zones for Cross-account Multi-region Architectures

AWS Disaster Recovery

Route 53 Private Hosted Zones (PHZs) and Resolver endpoints on AWS create an architecture best practice for centralized DNS in hybrid cloud environment. This blog presents an architecture that provides a unified view of the DNS while allowing different AWS accounts to manage subdomains. Architecture Overview.

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part IV: Multi-site Active/Active

AWS Disaster Recovery

The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. To maintain low latencies and reduce the potential for network error, serve all read and write requests from the local Region of your multi-Region active/active architecture. DR strategies.