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

Understanding cost optimization automation and policies

Before we address how to control and monitor costs, we need to know the details of how our costs are distributed across business applications.

In large enterprises, it's pretty normal to have a few core applications that spend about 20% more than others and waste a little bit of compute or memory resources: core applications need to be instantly available, thus we need more contingency compared to the non-critical ones, despite every possible horizontal scaling architecture you can realize.

So, the first thing to know when you migrate an application from on-premises to a cloud infrastructure is how the applications work, their flow, dependencies, and so on, and identify all the resources involved in that application, to better concentrate at a later stage on the component's optimization.

Important Note:

If you don't know how the application is composed and how it works, it's quite unlikely you will...