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

Getting started with Azure Bicep

At the time of writing, Azure Bicep is still in early development and not production ready yet, but this could change by the time you read this.

The main purpose of Azure Bicep is to do the following:

  • Alleviate the complexity of the ARM template language to make it less verbose and to bring a more developer-friendly approach.
  • Compiling Bicep files to produce a single ARM template. This prevents the use of a storage account or any other publicly available location for storing linked templates.

Unlike Terraform, Bicep remains Azure-specific. You can think of it as the next generation of the ARM language. To know more about Bicep and to stay tuned, you should subscribe to the Azure Bicep repo at Now we will redeploy exactly what we deployed previously, but we'll use raw ARM templates and evaluate the benefits of using Bicep. In order to perform this exercise, you must go through the following steps...