Remove Application Remove Architecture Remove Whitepaper
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.

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.

Insiders

Sign Up for our Newsletter

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

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

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.

article thumbnail

AI and Enterprise IT: How to Embrace Change without Disruption

Pure Storage

AI and Enterprise IT: How to Embrace Change without Disruption by Pure Storage Blog AI will be disruptive to enterprises, but how will it be disruptive to the enterprise IT architectures that support them? That’s in part because the AI application lifecycle is more iterative than traditional enterprise applications.

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. Application consistent replicas of MS SQL instances are achieved using the Microsoft VSS SQL Writer service. Read the full whitepaper on Protecting Oracle databases on VMware with Zerto.

article thumbnail

Types of Backup: Select Wisely to Avoid Costly Data Loss

Zerto

Perform an entire site or application failover, failback, and move without data loss or impact to production. There are additional differentiators like: Application-centric recovery for multi-VM applications. Recover an entire application and all its VMs to one single, consistent point in time.

Backup 98