Remove Application Remove Architecture Remove Disaster Recovery Remove Whitepaper
article thumbnail

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

AWS Disaster Recovery

In my first blog post of this series , I introduced you to four strategies for disaster recovery (DR). The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. I use Amazon DynamoDB for the example architecture in Figure 2.

article thumbnail

Understand resiliency patterns and trade-offs to architect efficiently in the cloud

AWS Disaster Recovery

Firms designing for resilience on cloud often need to evaluate multiple factors before they can decide the most optimal architecture for their workloads. Example Corp has multiple applications with varying criticality, and each of their applications have different needs in terms of resiliency, complexity, and cost. Trade-offs.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Minimizing Dependencies in a Disaster Recovery Plan

AWS Disaster Recovery

The Availability and Beyond whitepaper discusses the concept of static stability for improving resilience. What does static stability mean with regard to a multi-Region disaster recovery (DR) plan? In the simplest case, we’ve deployed an application in a primary Region and a backup Region.

article thumbnail

Journey to Adopt Cloud-Native Architecture Series: #3 – Improved Resilience and Standardized Observability

AWS Disaster Recovery

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.

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.

article thumbnail

How to Protect Your Database with Zerto

Zerto

Database contents change depending on the applications they serve, and they need to be protected alongside other application components. Zerto, a Hewlett Packard Enterprise company, simplifies the protection of a business’s most precious assets by providing disaster recovery for databases at scale.

article thumbnail

Types of Backup: Select Wisely to Avoid Costly Data Loss

Zerto

These backup appliances are also dabbling in delivering disaster recovery capabilities using VM snapshots. Apart from traditional VM backup, software-based backup solutions are also looking to deliver disaster recovery capabilities using VM snapshots. Scale-out architecture, scale from a few VM to thousands with ease.

Backup 94