Chapter 39. Never Take a Single Region Dependency
Derek Martin
Enterprises of all shapes and sizes frequently make a tragic mistake when migrating to the cloud: “Hooray, I no longer have to have a disaster response or business continuity plan; Microsoft/AWS/Google will take care of it!” It’s true, the cloud is a highly resilient place to migrate your enterprise to; but at its most basic, even the cloud is composed of physical servers and run by human beings. Things break, catch fire, go boom, and are occasionally susceptible to human error. So, when migrating to the cloud, take this first and most important lesson with you: never take a single region dependency!
Azure provides a variety of solutions to help you be successful, including these:
- Redundant storage
- Keep multiple copies of your data in multiple physical locations.
- Availability zones
- Run your solutions in multiple data halls/facilities in a single region.
- Backup
- Enable file-level restorations for when files go missing.
- Site recovery
- Fail over VMs from one region to another with a very tight recovery time objective/recovery point objective (RTO/RPO).
Each stock-keeping unit (SKU) within Azure takes a slightly different approach to regional resiliency, and your enterprise needs to consider those methodologies for each of your applications. For example, Azure ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access