Application Architecture Whitepaper 
AWS Disaster Recovery
JUNE 3, 2022
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.
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.
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. 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.
Zerto
JANUARY 24, 2023
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.
Pure Storage
JANUARY 29, 2024
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.
Zerto
SEPTEMBER 3, 2021
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.
Expert insights. Personalized for you.
128 
Let's personalize your content