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 high availability and disaster recovery

First of all, let's review the difference between high availability and disaster recovery and put that in the Azure context. A high availability (HA) solution is continuously available for a desired amount of time. In Azure, most HA solutions are scoped to a single geographical region.

Disaster recovery (DR) aims to recover from a severe incident, such as a fire (or flooding) in the data center, an earthquake, or any other type of heavy damage. In Azure, an example of a severe outage is the complete unavailability of an entire region, or of a service within a region. DR-compliant systems often rely on multiple regions, which incurs extra costs. Usually, a design that is DR-compliant is also HA.

Whether you design a solution for HA or DR depends on the expected recovery time objective (RTO) and recovery point objective (RPO) defined by the business or expected by your customers (if you provide the service). Figure 3.13...