Cost optimisation: The new capacity management
Capacity management has been an IT Service Management (ITSM) staple for years, often historically associated with practices such as Just In Time (JIT) hardware provision to achieve network, storage or compute low watermarks which sustain Service Level Agreements (SLAs). However, as the move to commodified on-demand workload prevails – as enabled through Cloud and DevOps provisioning practices – capacity management becomes less optimal as a practice to sustain the delicate balance of cost versus performance for an IT system.
With the increased adoption of Cloud native giving rise to OpEx, rental-based workload hosting over CapEx and ownership-based workload hosting, we’re seeing a new contender for managing performance against cost in the IT Services space: cost optimisation.
What are the benefits of cost optimisation?
Cost optimisation is the process of identifying and reducing sources of wasteful spending, underutilisation, or low return in the IT budget. The goal is to reduce costs while reinvesting in new technology to speed up business growth or improve margins. Unlike capacity management, cost optimisation focuses on system architecture improvements and modifications and tweaking computer, storage and network levers to achieve its goal.
In the Cloud context, cost optimisation often looks like a FinOps team, process or mandate, tasked with the following to achieve cost reductions:
- Identify and reduce mismanaged or excess resources
- i.e. Identify Azure VM Scale Sets with overprovisioned and unused Azure Virtual Machine members
- Take advantage of advance purchase discounting options where lifecycle is prolonged
- i.e. Purchase AWS EC2 Reserved Instance pricing for a three-year term to achieve a >60% cost saving against on-demand EC2 pricing
- Take advantage of Cloud-complimentary licensing schemes for IaaS
- i.e. Utilise Azure Hybrid User Benefit (HUB) to achieve ~70% cost saving of an Azure SQL instance using existing on-premises Microsoft SQL Licensing
- Right size compute, storage or network workloads to specific requirements
- i.e. Swap-out an underutilised, low-IO Azure Premium SSD for an Azure Standard SSD
Much of this runs contrary to traditional capacity management practices, as the main vehicles of achieving these are often to rearchitect elements of how the IaaS or PaaS components operate to achieve improvements in upper-layer application workloads.
Ideally, you want your Cloud infrastructure costs to go flat or increase only marginally as your client or installed application workload base grows, but if your costs rise faster than – or as quickly as – you onboard customers, you may have a problem. Cost optimisation can therefore be a great way to build a scalable, modern infrastructure that meets the demands of your workloads without going over budget.
Shifting away from capacity management
Capacity management has traditionally focused on ensuring that IT systems have the resources they need to perform optimally against a backdrop of on-premises IT where Baremetal was king and OpEx was reserved purely for Software Licensing concerns. However, this approach is no longer sufficient in today’s complex IT environments, where ephemeral workloads and infrastructure elasticity mean it can be difficult to keep track.
By shifting from capacity management to cost optimisation, organisations can better align their increasingly limited IT spending with business priorities. This approach involves identifying areas where costs can be reduced without sacrificing the important Observability Pillars of Performance or Reliability.
Best practices for achieving cost optimisation
Being successful with cost optimisation initiatives requires a cultural shift – as enabled via DevOps and Agile Project Management practices – towards these best practices:
Align initiatives with business priorities
Cost optimisation initiatives should be aligned to the business’ overall priorities to avoid “penny-wise and pound-foolish” behaviours (i.e. skimming pennies off AWS EBS disk size, when an exponentially-more-cost-effective AWS S3 bucket would be a better fit for an object storage challenge instead).
Identify and right-size over-provisioned resources
Using the right tools (such as Zesty, Spot, nOps and Harness) to identify, optimise scale-down and turn off over–provisioned infrastructure, including automated optimisation.
Be accountable for infrastructure costs using chargeback, recharge or show-back
Cost accountability must be clearly articulated and factored into the RACI for required stakeholders to be aware of their business unit’s impact on overall IT infrastructure spend.
Take action to optimise spend
Much like “security by design”, spend by design should be an upfront factor in the IT infrastructure or network design process from Day 0 design rather than a Day 2 operations afterthought.
Use the right tool for the right job
When architecting a system, care should be given to tooling selection and “on-premises bias”. For instance, AWS S3 is a fantastic cost-efficient choice for static asset (Image/CSS/etc.) storage which doesn’t exist on-premises, so might otherwise be approximated with a more costly solution like an AWS EBS or AWS EFS Network-based file store via AWS EC2 to achieve the same at a much higher cost.
Overall, cost optimisation isn’t a one-shot activity. It is a continuous process to enable optimal business operations and garner cost efficiency. Cloud waste reduction should always be the goal to finance growth in desired USP and differentiators.
Continuing the efficiency
Gartner predicts Cloud spending to grow to almost $600 billion in 2023, with earlier trends showing the Cloud TAM (Total Addressable Market) having increased year-on-year at a rate of 20-30%. In 2026, Public Cloud expenditure is estimated to be as much as half of all enterprise IT budget spending. Unlike on-premises infrastructure, which can be amortised and deprecated over time, Cloud spend tends to be ongoing operational expenditure (OpEx) and can often increase over time for a given workload as its use or client base grows.
If you want those flat or diminished infrastructure costs, you must integrate cloud optimisation into your business processes and daily workflow. Cloud optimisation isn’t a “one and done” endeavour. To be truly mature in cloud optimisation, we would advocate for FinOps practices to be engrained into the CI/CD pipelines and ITSM governance gating processes – such as Design Board, CAB and ITDB – to treat it as a first-class citizen amongst other competing factors within the system operation and design.
Cost optimisation should exist to answer these questions in returning value to the business:
- How much does each product feature or enterprise application cost to operate over time?
- What is the unit cost of infrastructure compared to gained functionality?
- How high is our utilisation cost per customer (for a SaaS Company) or application (for an enterprise) per end user?
- Can we reduce the performance tiers of compute, storage or network components to cheaper variants without reducing perceived SLA and OLA commitments?
- Do our development workloads operate to sensible development-sized smaller or less-performant IaaS or PaaS components?
- Can we proof of concept (PoC) under-provisioning against enterprise application workload system requirements to measure the actual impact – if any – on the SLA and OLAs our end users are signed up to?
- Can we utilise economies of scale to make more infrastructure components cost less on aggregate?
- Think along the lines of “Domino’s Promo-Codeconomics” – adding a 49p dip to your Domino’s order to push it over £50 so the “20% off £50” promo code takes affect
How CACI can help you finesse your FinOps
CACI Network Services is well versed in using cost optimisation techniques to provide the best value for countless types of enterprise and application workload architectures, through our strong heritage in Network Infrastructure Engineering and Consulting.
Get in touch and let our experts work alongside your FinOps teams to tame your Cloud bills and impart our cloud optimisation know-how and learnings from industry.