Book Image

The Azure Cloud Native Architecture Mapbook

By : Stéphane Eyskens, Ed Price
Book Image

The Azure Cloud Native Architecture Mapbook

By: Stéphane Eyskens, Ed Price

Overview of this book

Azure offers a wide range of services that enable a million ways to architect your solutions. Complete with original maps and expert analysis, this book will help you to explore Azure and choose the best solutions for your unique requirements. Starting with the key aspects of architecture, this book shows you how to map different architectural perspectives and covers a variety of use cases for each architectural discipline. You'll get acquainted with the basic cloud vocabulary and learn which strategic aspects to consider for a successful cloud journey. As you advance through the chapters, you'll understand technical considerations from the perspective of a solutions architect. You'll then explore infrastructure aspects, such as network, disaster recovery, and high availability, and leverage Infrastructure as Code (IaC) through ARM templates, Bicep, and Terraform. The book also guides you through cloud design patterns, distributed architecture, and ecosystem solutions, such as Dapr, from an application architect's perspective. You'll work with both traditional (ETL and OLAP) and modern data practices (big data and advanced analytics) in the cloud and finally get to grips with cloud native security. By the end of this book, you'll have picked up best practices and more rounded knowledge of the different architectural perspectives.
Table of Contents (13 chapters)
Section 1: Solution and Infrastructure
Section 2: Application Development, Data, and Security
Section 3: 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...