Calculating the Operations Cost of Software You Haven't Developed
summary
Enterprise maps microservice performance to cost by automating load tests with TeamCity and JMeter, recording CPU/memory utilization and how many resources (VM/container sizes) meet targets. Example: a service required 400 tps under 100 ms so tests find the minimal VM size; experiment rollouts use 5% traffic to size for 100 tps under 150 ms. Empirical extrapolation cuts a blunt £4M guess to about £400k — an order of magnitude reduction.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:26easyJet
- 2:22John Eric Davis
- 2:51how much will it cost?
- 3:43what hardware do we need to buy?
- 4:24budget structure
- 4:54problems
- 5:46improvements
- 6:36microservices
- 9:03performance
- 9:54testing
- 11:16requirement
- 14:51forecast
- 15:32alternate loads
- 16:28alternate resources
- 17:17Recommendation Service
- 21:26costs
- 23:52summary
related talks
20mHow to Think About Instrumentation Overhead
29mMaking the Business Case for DevOps
35mAzure SpendOps – The Art of Effectively Managing Azure Costs
15mPlatform Engineering - a 1 mln $ worth change
49mAssessing and Optimize Enterprise SQL Server Environments
33mPerformance Testing in Agile and DevOps
43mBuilding Monetary Confidence in the Cloud
41mPerformance Engineering in the Age of DevOps and Agile