Summary
In this chapter, we concluded Part 4, Applications and Databases by looking at the options for introducing high availability into our solutions.
Although many Azure components provide a redundancy level by default, some services require availability to be designed in, and others offer different levels of resilience depending on your needs.
We also looked at how we can apply these concepts to Azure VMs using scale sets, which enable us to automate the scaling of VMs based on demand and thresholds we can set.
We also looked at the different Azure storage accounts and databases, namely Azure SQL and Azure Cosmos DB. These services provide a default level of local redundancy, meaning you are protected against hardware failure. However, we examined how this can be extended across regions should it be required.
In the next chapter, we begin Part 5, Operations and Monitoring, starting with the different ways to set up logging and monitoring components.
