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

Developing microservices

Our objective in this section is to give you a glimpse of developing cloud-native applications. Microservices are 100% cloud-native par excellence, hence the reason why we use them to illustrate our purpose. We will not cover the entire spectrum of microservices, because the topic deserves an entire book on its own. We assume that you know already what microservices are, and we will focus on some technical bits only.

In Chapter 3, Infrastructure Design, we reviewed the different infrastructure options at our disposal to host microservices. Our conclusion was that, at the time of writing, in Azure, AKS is the most suitable choice. We stressed the fact that service meshes play a great role in terms of the observability, security, deployment, and resilience of a microservices architecture. We also highlighted some AKS-killing features, such as self-healing, cluster, and pod auto-scaling, to name a few. All of these infrastructure features help to build resilient...