The "worst best deal", and how engineering should be the driver for FinOps success.
In most cases, we see a lot of FinOps practitioners measuring their reservation coverages, Spot usage, and other financial plans to run on the "most optimized" pricing plans. Financial optimization became the new goal of companies practicing #finops, committing to lower rates to try and get, what we call at Wix, the "worst best deal".
What it means, in most cases, is that they prefer to cover wasteful activities to mitigate their costs, instead of investing the engineering and business effort to understand the specific workload's value. I've seen companies investing a month of engineering effort to better understand what is their *needed* capacity, instead of *used* capacity. They put a "value" KPI on their workload, other than its cost.
Wiz's use case for example is inspiring, reducing 30% of their costs
AppsFlyer's use case is also impressive with an 85% reduction
Or even how Wix implemented their own "Intelligent-Tierng"/"Autoclass" solution - Way before it was cool 😎
Engineers understanding the value of their workload, and understanding the financial KPI as well as how to run more efficiently, will be the level of engineering companies will hire over "traditional" engineers in the coming future.
This is the actual power of FinOps and the evolution of what advanced practice looks like.
Thoughts?