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

What not to do

We’ve shown what is to be done, so let’s see what shouldn’t or mustn’t be done. These are the common pitfalls and anti-patterns – the things that may seem obvious and perfectly acceptable but that nevertheless aren’t.

Here are some anti-patterns to avoid (in random order):

  • Accumulating technical debt without justification and a plan to address it – this is never a good idea anyway, but it is especially bad if the cloud adoption is trying to address and improve the time-to-market. Remember, if you are building it or you’ve built it and it isn’t in the hands of your customers, what good did any of that effort do?
  • Lift-and-shift with no modernization plans – the cloud wasn’t meant for this, except in a very narrow case of maintenance and no further development until the service gets decommissioned. That is the only acceptable case of lift-and-shift.
  • Assessing the skills available...