Remove Application Remove Architecture Remove Failover
article thumbnail

Top Architecture Blog Posts of 2024

AWS Disaster Recovery

Weve watched in awe as the use of real-world generative AI has changed the tech landscape, and while we at the Architecture Blog happily participated, we also made every effort to stay true to our channels original scope, and your readership this last year has proven that decision was the right one. Well, its been another historic year!

article thumbnail

Creating an organizational multi-Region failover strategy

AWS Disaster Recovery

You can use these fault boundaries to build multi-Region applications that consist of independent, fault-isolated replicas in each Region that limit shared fate scenarios. However, applications typically don’t operate in isolation; consider both the components you will use and their dependencies as part of your failover strategy.

Failover 117
Insiders

Sign Up for our Newsletter

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

article thumbnail

Considerations for Disaster Recovery – Part 3: Networking

Zerto

Recovery Time Objective (RTO): Measures the time it takes to restore applications, services, and systems after a disruption. BGP, OSPF), and automatic failover mechanisms to enable uninterrupted communication and data flow. Are advanced security measures like zero trust architecture in place? Do you conduct regular DR tests?

article thumbnail

Considerations for Disaster Recovery – Part 2: Compute

Zerto

Being able to choose between different compute architectures, such as Intel and AMD, is essential for maintaining flexibility in your DR strategy. Zerto excels in this area by offering an agnostic approach to DR, ensuring flexibility and compatibility across various platforms, whether you are using Intel or AMD architectures.

article thumbnail

Creating a Multi-Region Application with AWS Services – Part 1, Compute and Security

AWS Disaster Recovery

Building a multi-Region application requires lots of preparation and work. Many AWS services have features to help you build and manage a multi-Region architecture, but identifying those capabilities across 200+ services can be overwhelming. Finally, in Part 3, we’ll look at the application and management layers.

article thumbnail

Creating a Multi-Region Application with AWS Services – Part 2, Data and Replication

AWS Disaster Recovery

In Part 1 of this blog series, we looked at how to use AWS compute, networking, and security services to create a foundation for a multi-Region application. Data is at the center of many applications. For this reason, data consistency must be considered when building a multi-Region application.

article thumbnail

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

AWS Disaster Recovery

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.