How do you measure the value of DevOps when every project is different? In this case-study style webinar, Fedir Kompaniiets, co-founder of Gart Solutions, explains how to pick the right metrics for your business model, where infrastructure budgets go wrong, and how to justify DevOps investment to management.
Who it is for:
Founders, CTOs and project owners planning DevOps work or trying to keep infrastructure budgets under control.
Key takeaways
- DevOps metrics should follow business objectives: for an online SaaS platform downtime and deployment frequency matter most, while for an internal data platform stability and data consistency matter more.
- Identify future cost drivers early. For example, a gambling platform that is cheap to run at launch can face large traffic bills on AWS as users grow.
- The cheapest infrastructure usually means the most expensive maintenance: managed cloud services cost more but need fewer engineering hours.
- DevOps works when everyone follows the same strict process, with no back doors.
- Startup cloud credits can lead to lock-in: services pile up while they are free, and moving away later needs extra development and budget.
Timestamps
- 0:03 Introduction
- 1:07 What DevOps really means
- 2:11 Business objectives first: metrics differ by project
- 5:26 Budget control and hidden infrastructure costs
- 7:34 Cheap infrastructure vs expensive maintenance
- 8:41 People, money and time
- 9:44 Where to start: industry reports and a DevOps audit
- 11:54 Q&A: a resource management framework for an environmental platform
- 14:01 Q&A: how to justify the cost to management
- 15:08 Q&A: getting development and operations to follow one process
- 17:15 Q&A: budget traps such as startup cloud credits
Speakers
Fedir Kompaniiets, Co-founder, Gart Solutions
Related resources
- DevOps audit
- Cost-effectiveness in DevOps and cloud
- 20 cloud cost optimization traps
- DevOps consulting
Want to discuss how this applies to your infrastructure?
Talk to our team, or browse all Gart Solutions webinars.
