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

Introducing Continuous Integration and Continuous Deployment (CI/CD)

Before diving into CI/CD, let's first step back and reflect on what DevOps means. In most large organizations, the IT department is still divided into siloes. The most common ones are the developers, on the one hand, and the infrastructure teams on the other. You might as well have a separate security team and some middle ground bodies, overseen by a governance body and an enterprise architecture practice. The purpose of DevOps is to act as a bridge between the teams and to break the silo mentality. DevOps is part of a broader digital transformation program that may take years to achieve. The whole point behind digital transformation and DevOps is to gain extra agility and efficiency. However, that's easier said than done!

While the theory is promising, the reality often tends to prove otherwise: resistance of the different teams, misunderstandings on the part of management, a lack of proper skills, people...