Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Azure Infrastructure Services for Architects

You're reading from   Microsoft Azure Infrastructure Services for Architects Designing Cloud Solutions

Arrow left icon
Product type Paperback
Published in Oct 2019
Publisher Wiley
ISBN-13 9781119596578
Length 448 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
John Savill John Savill
Author Profile Icon John Savill
John Savill
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

1. Cover FREE CHAPTER
2. Acknowledgments
3. About the Author
4. Introduction
5. Chapter 1 The Cloud and Microsoft Azure Fundamentals 6. Chapter 2 Governance 7. Chapter 3 Identity 8. Chapter 4 Identity Security and Extended Identity Services 9. Chapter 5 Networking 10. Chapter 6 Storage 11. Chapter 7 Azure Compute 12. Chapter 8 Azure Stack 13. Chapter 9 Backup, High Availability, Disaster Recovery, and Migration 14. Chapter 10 Monitoring and Security 15. Chapter 11 Managing Azure 16. Chapter 12 What to Do Next 17. Index
18. End User License Agreement

High Availability in Azure

I covered a lot of the key concepts at the start of this chapter when it comes to thinking about high availability (HA). Typically, HA is thinking about keeping a service available and resilient within a region. For many services, such as storage, this is built-in. For example, Azure Storage (with its three synchronous copies), Azure SQL Database, and Cosmos DB also have resiliency built-in. For the Platform as a Service options, HA is native, and all that is required is to have at least two instances.

For IaaS VMs, you need to be able to have at least two instances. This is a minimum; three is preferred, as you have to consider there are times when there is planned maintenance, rendering a certain percentage unavailable, or a failure. If you only have two instances, then you are down to one, meaning you cannot tolerate any other problem. Having three instances enables something to happen and you still have a level of resiliency left. Since the VMs will likely...

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