Summary
In this chapter, we did a vertical exploration of infrastructure practice in Azure. We covered several topics, such as networking, monitoring, backup and restore, high availability, and disaster recovery for both Azure itself and AKS. We made it clear that AKS is a special service that comes with its own practices and ecosystem. As an Azure infrastructure architect, you should pay special attention to AKS, whenever it lands on your plate. Our message here is this: yes, use AKS – but do not overlook its complexity and particularities.
In this chapter, we also explored two concrete use cases. The first one demonstrated how challenging (and costly) it can be to have a consistent and coherent disaster recovery strategy for a global API deployment. The second one was about using AKS for microservices. We explained why we think that AKS is more suitable than pure Azure-native services for large microservices implementations. We concluded with a reference architecture for...
