Book Image

The Road to Azure Cost Governance

By : Paola E. Annis, Giuliano Caglio
Book Image

The Road to Azure Cost Governance

By: Paola E. Annis, Giuliano Caglio

Overview of this book

Cloud teams and ICT cost controllers working with Azure will be able to put their knowledge to work with this practical guide, introducing a process model for structured cost governance. The Road to Azure Cost Governance is a must-read if you find yourself facing the harsh reality of monthly cloud costs gradually getting out of control. Starting with how resources are created and managed, everything you need to know in order to track, display, optimize, rightsize, and clean up cloud resources will be tackled with a workflow approach that will leave the choice of operation to you (be it the Azure CLI, automation, logic apps, or even custom code). Using real-world datasets, you'll learn everything from basic cost management to modeling your cloud spend across your technical resources in a sustainable way. The book will also show you how to create a recursive optimization process that will give you full control of spending and savings, while helping you reserve budget for future cloud projects and innovation. By the end of this Azure book, you'll have a clear understanding and control of your cloud spend along with knowledge of a number of cost-saving techniques used by companies around the world, application optimization patterns, and the carbon impact of your cloud infrastructure.
Table of Contents (14 chapters)
Section 1: Cloud Cost Management
Section 2: Cloud Cost Savings
Section 3: Cost- and Carbon-Aware Cloud Architectures

Application performance optimization

Having fully optimized your databases against your infrastructure is, unfortunately, sometimes not enough. If your application is running in Azure, it probably came from one of the most common migration patterns:

  • Lift and shift: You took the application and moved it to cloud resources without changing anything. This is typically the most expensive pattern infrastructure-wise as matching on-premises resources within the cloud is a time-consuming and often useless activity in terms of modernization, since you will often just move your legacy app somewhere else.
  • Refactor: You made small changes in the code and probably took advantage of a few PaaS products and now have a mix of old and new cloud objects, as well as a roadmap to something more modern.
  • Rearchitect: Chances are you cannibalized the original application toward a microservices solution, which is much better than the preceding two patterns, but even if this dramatically reduces...