Book Image

Azure Cloud Adoption Framework Handbook

By : Sasa Kovacevic, Darren Dempsey
Book Image

Azure Cloud Adoption Framework Handbook

By: Sasa Kovacevic, Darren Dempsey

Overview of this book

You've heard about the benefits of the cloud and you want to get on board, but you’re not sure where to start, what services to use, or how to make sure your data is safe. Making the decision to move to the cloud can be daunting and it's easy to get overwhelmed, but if you're not careful, you can easily make mistakes that cost you time and money. Azure Cloud Adoption Framework Handbook is here to help. This guide will take you step-by-step through the process of making the switch to the Microsoft Azure cloud. You’ll learn everything from foundational cloud concepts and planning workload migration through to upskilling and organization transformation. As you advance, you’ll find out how to identify and align your business goals with the most suitable cloud technology options available. The chapters are designed in a way to enable you to plan for a smooth transition, while minimizing disruption to your day-to-day operations. You’ll also discover how the cloud can help drive innovation in your business or enable modern software development practices such as microservices and CI/CD. Throughout the chapters, you’ll see how decision makers can interact with other internal stakeholders to achieve success through the power of collaboration. By the end of this book, you’ll be more informed and less overwhelmed about moving your business to the cloud.
Table of Contents (15 chapters)
Part 1: The Why
Part 2: The Plan
Part 3: The Execution and Iteration

Architecture reviews

A great start when architecting a workload is the Azure reference architectures page:

Your workloads are special, but it is very unlikely you are doing something never seen before, so check and see whether one of these can give you a jump-start toward your end architecture.

So, how do you perform architecture reviews?

The intent behind architecture reviews of reliability, cost management, operational excellence, performance efficiency, and security is to ensure architecture is unified, non-functional requirements are considered and implemented, and everyone is on the same page.

You will need to plan the cadence, which, depending on the speed and the volume of change in your organization, might be from every two weeks to every quarter. Err on the side of two weeks; you can always cancel the review if there are no changes.

Here is an example of a quarterly plan from one SRE team (as an example...