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

Zooming in on a reference architecture with Azure DevOps

So far, we have reviewed the fundamentals of Terraform, ARM templates, and Azure Bicep. It is now time to see how you can concretely set up a factory that's designed to provision resources and deploy applications in an industrial manner. Of course, we will not walk you through the complete setup, but we will describe the possible approaches.

Beware that it takes time to get a fully industrialized factory up and running, and it is a significant investment. So far, we have largely focused on the IaC bits, but of course the infrastructure components that we provision are used by applications that have their own life cycle. At the end of the day, you need to find a way to deploy both the application code and the infrastructure together, while still being able to test your own infrastructure work, independently of the applications that will consume your components. Therefore, we must distinguish the authoring and versioning...