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

Revisiting our architectures

First, we'll revisit our architectures by summarizing each chapter of the book. This allows the opportunity to refresh your memory and offer a key appeal from each chapter, one important takeaway that could greatly impact your cloud architectures.

Sample architecture

In Chapter 1, Getting Started as an Azure Architect, we explained the basic idea behind the maps in this book, why we're using them, and how you can use them to further explore architectures. We provided a sample map (see Figure 8.1) to properly explain how the maps are structured:

Figure 8.1 – Our sample map

Figure 8.1 – Our sample map

The sample map demonstrates the subdomains, concerns, options, and alternatives. Our larger-level architecture map focuses on the master domain and subdomains. When we zoomed in, we showed you a fuller map that includes the concerns under a given subdomain. Next, we browsed the different types of architects and showed you what makes...