article thumbnail

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

AWS Disaster Recovery

As a refresher from previous blogs, our example ecommerce company’s “Shoppers” application runs in the cloud. Earlier, we were able to restore from the backup but wanted to improve availability further. This allows us to adjust capacity needs by forecasting usage patterns along with configurable warm-up time for application bootstrap.

article thumbnail

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

AWS Disaster Recovery

Then we explored the backup and restore strategy. In addition to replication, both strategies require you to create a continuous backup in the recovery Region. Backups are necessary to enable you to get back to the last known good state. The warm standby strategy deploys a functional stack, but at reduced capacity.