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)
1
Section 1: Solution and Infrastructure
6
Section 2: Application Development, Data, and Security
10
Section 3: Summary

AKS infrastructure

AKS is an entire world within the Azure universe. This is by no means a service like the others. It is a partly managed service, as shown in Figure 3.18.

Figure 3.18 – AKS, a semi-managed service

Figure 3.18 – AKS, a semi-managed service

The control plane is the brain of AKS, and it is fully managed by Microsoft for free. Your duty as an Azure infrastructure architect is to take care of the worker nodes, which are plain virtual machines, connected to the brain via kubelet, the Kubernetes (K8s) primary node agent. It runs on each node, and the agent registers the node with the API server automatically. Rest assured, Azure comes with pre-defined node images, and you do not have to build the worker nodes yourself, just manage them. Although self-hosting a K8s cluster is even more demanding, you should not neglect the number of operations left to the cloud consumer when working with AKS. Unlike a fully managed PaaS or FaaS service, AKS requires special care and upfront analysis...