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)
1
Section 1: Solution and Infrastructure
6
Section 2: Application Development, Data, and Security
10
Section 3: Summary

Analyzing traditional data practices

In this section, we will review services that belong to the traditional data world. Our purpose is to reassure you that what we can do on-premises can also be done the same way in the cloud. Moving data workloads to the cloud does not necessarily mean that you have to completely reinvent yourself and your way of working.

Let's first clarify that we do not use the term traditional in a pejorative (nor negative) way. In many situations and for many enterprises, using traditional techniques still provides full satisfaction, and you should not necessarily move to more modern technologies just for the sake of it. (Our point has been made!) Figure 6.2 displays our zoom-in on traditional data practices:

Figure 6.2 – Traditional data practices in Azure

Figure 6.2 – Traditional data practices in Azure

The TRADITIONAL node regroups all traditional practices that we've typically used for decades, for which Azure also has a bunch of services that we will discuss...