Cost optimization design principles

Business goals and the return on investment (ROI) drive a cost-effective workload while you keep to a given budget. The principles of cost optimization are important considerations that help you achieve both business objectives and cost justification.

To assess your workload using the tenets you find in the Azure Well-Architected Framework, see the Microsoft Azure Well-Architected Review.

The following design principles provide:

  • Context for questions
  • Why a certain aspect is important
  • How an aspect applies to cost optimization

Use these critical design principles as lenses to assess the cost optimization of an application deployed on Azure. These lenses provide a framework for the application assessment questions.

Choose the correct resources

Choose resources that align with business goals and can handle your workload performance.

When onboarding new workloads, explore the possibility of modernization and cloud native offerings where possible. It's typically more cost-effective to use platform as a service (PaaS) or software as a service (SaaS), as opposed to infrastructure as a service (IaaS).

An inappropriate or misconfigured service can affect cost. For example, building a multi-region service when the service levels don't require high-availability or geo-redundancy increases cost without any reasonable business justification.

Set up budgets and maintain cost constraints

Every design choice has cost implications. Consider the budget constraints set by the company before choosing:

  • An architectural pattern
  • The Azure service
  • A price model for the service

As part of design, identify acceptable boundaries on:

  • Scale
  • Redundancy
  • Performance against cost

After estimating the initial cost, set budgets and alerts at different scopes to measure the cost. One cost driver can be unrestricted resources. These resources typically need to scale and consume more cost to meet demand.

Dynamically allocate and deallocate resources

To match performance needs, dynamically allocate and deallocate resources.

Identify idle or underutilized resources through Azure Advisor or other tools, and:

  • Reconfigure
  • Consolidate (or)
  • Shut down

Optimize workloads, aim for scalable costs

A key benefit of the cloud is the ability to scale dynamically. The workload cost should scale linearly with demand. You can save cost through automatic scaling.

Recommendations:

  • Consider usage metrics and performance to determine the number of instances.
  • Choose smaller instances for a highly variable workload.
  • Scale out, rather than up, to get the required level of performance. This choice enables you to make your cost calculations and estimates granular.

The cost management process should be:

  • Rigorous
  • Iterative
  • A key principle of responsible cloud optimization

Continuously monitor and optimize cost management

To provision resources dynamically and to scale with demand:

  • Conduct regular cost reviews
  • Measure capacity needs
  • Forecast capacity needs

If you're just starting this process, review enable success during a cloud adoption journey.

Next step