Keynote: The Cost of Agility at Scale: It's All Fun and Games Until the Bill Comes
summary
Cloud-native speed creates big bills unless teams measure and design for cost: a real case shows 107 CPU years in a month from unchecked Lambda invocations, and a 90% saving by switching to a few long‑running instances. Advice includes tagging consistently, making cost forecasts for each change, understanding data lifecycle to avoid expensive analytics on cold object storage, and automating cleanup such as tear down staging automatically to avoid wasted resources.
AI-written summary · about
chapters (7)
- 0:00Introduction and keynote setup
- 1:24Engineering pride and architecture displays
- 3:52Common velocity-focused problems
- 6:22Cost surprises and unit economics
- 8:27Key strategies for cost control
- 10:57Architecture agnosticism and debt
- 13:32Summary and closing remarks
related talks
30mAnd the CFO Wept: AWS Cost Control
31mThe irony of cloud cost-cutting: when saving money leads to losing money
34mGame Over on the Bill: Playing the Cost Tetris in Kubernetes
20mAtomics Habits in cost optimizations in the cloud
05mFive Minute Cost-Optimisation
21mBest Practices for Optimizing Your Cloud Spend with AI
14mKeynote: The Big Leap: Conquering the Legacy System and Building a Scalable Cloud...
45mMoney, money, money... Fu!@, it isn't funny!