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 described the solution architecture map and its different classification categories, which are SoE, SoR, SoI, and systems of interaction (IPaaS). This categorization, commonly used in architecture, makes it easier to dispatch services. We provided explanations and extra-focused maps, which helped further refine the alternatives.

We also emphasized the importance of cross-cutting concerns that apply to every solution, and we discussed which concerns should be considered by solution architects. Remember that it might be too challenging to address all of the concerns on day one of your cloud journey. It is, therefore, interesting to think of different maturity levels, and how we would put them on a roadmap to manage our stakeholders' expectations.

Next, we highlighted the containerization components, with a focused map that depicted the container landscape of Azure. We also considered other dimensions, such as cost, complexity, and the level of residual...