Remove Architecture Remove Capacity Remove Whitepaper
article thumbnail

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

AWS Disaster Recovery

Figure 2 shows the four strategies for DR that are highlighted in the DR whitepaper. Architecture of the DR strategies. Backup and restore DR architecture. Pilot light DR architecture. Warm standby DR architecture. Multi-site active/active DR architecture. Backup and restore. Pilot light.

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. Due to its monolithic architecture, the application didn’t scale quickly with sudden increases in traffic because of its high bootstrap time. Predictive scaling for EC2.

Insiders

Sign Up for our Newsletter

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

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. This will help you achieve varying levels of resiliency and make decisions about the most appropriate architecture for your needs. Looking for more architecture content?

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part III: Pilot Light and Warm Standby

AWS Disaster Recovery

The warm standby strategy deploys a functional stack, but at reduced capacity. If the passive stack is deployed to the recovery Region at full capacity however, then this strategy is known as “hot standby.” Disaster Recovery (DR) Architecture on AWS, Part I: Strategies for Recovery in the Cloud. Related information.

article thumbnail

Pure Storage Veeam Plugin

Pure Storage

This is due to the of the hypervisor’s underlying snapshot architecture, which introduces IO amplification due to the redirection of writes and the replay of a per-VM SCSI transaction log when the backup process completes. This architecture option dramatically reduces data restoration times for large data sets and critical applications.

Backup 52
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? The consensus was that new architectures should be designed not for specialization but for flexibility and disaggregation.

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? The consensus was that new architectures should be designed not for specialization but for flexibility and disaggregation.