Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Azure Cloud Native Architecture Mapbook

You're reading from   The Azure Cloud Native Architecture Mapbook Explore Microsoft Cloud's infrastructure, application, data, and security architecture

Arrow left icon
Product type Paperback
Published in Feb 2021
Publisher Packt
ISBN-13 9781800562325
Length 376 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Stéphane Eyskens Stéphane Eyskens
Author Profile Icon Stéphane Eyskens
Stéphane Eyskens
Ed Price Ed Price
Author Profile Icon Ed Price
Ed Price
Ed Price Ed Price
Author Profile Icon Ed Price
Ed Price
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Section 1: Solution and Infrastructure
2. Chapter 1: Getting Started as an Azure Architect FREE CHAPTER 3. Chapter 2: Solution Architecture 4. Chapter 3: Infrastructure Design 5. Chapter 4: Infrastructure Deployment 6. Section 2: Application Development, Data, and Security
7. Chapter 5: Application Architecture 8. Chapter 6: Data Architecture 9. Chapter 7: Security Architecture 10. Section 3: Summary
11. Chapter 8: Summary and Industry Scenarios 12. Other Books You May Enjoy

Zooming in on high availability and disaster recovery

First of all, let's review the difference between high availability and disaster recovery and put that in the Azure context. A high availability (HA) solution is continuously available for a desired amount of time. In Azure, most HA solutions are scoped to a single geographical region.

Disaster recovery (DR) aims to recover from a severe incident, such as a fire (or flooding) in the data center, an earthquake, or any other type of heavy damage. In Azure, an example of a severe outage is the complete unavailability of an entire region, or of a service within a region. DR-compliant systems often rely on multiple regions, which incurs extra costs. Usually, a design that is DR-compliant is also HA.

Whether you design a solution for HA or DR depends on the expected recovery time objective (RTO) and recovery point objective (RPO) defined by the business or expected by your customers (if you provide the service). Figure 3.13...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image