FinOps and Cloud Cost Optimization
summary
Claims concrete savings and failures: industry shows 28–32% cloud waste and reserved instances deliver ~40% (1yr) to ~60% (3yr) savings, spot instances and scheduling cut dev/test bills, and managed services plus autoscaling and ephemeral CI/CD reduce ops cost. Migration anti-patterns are lift‑and‑shift and oversized VMs; refactoring into containers, event‑driven functions, read replicas and tiered storage is measurable. An event‑driven product example runs for $1/mo and GPUs for models run serverless with token billing.
AI-written summary · about
chapters (9)
- 0:00FinOps and cloud cost basics
- 2:06What FinOps is and why it matters
- 7:15Cloud migrations and culture gaps
- 10:06Cost optimization with Well-Architected
- 13:18Quick cloud cost cuts
- 15:24Optimizing workloads and apps
- 19:32KPIs and hybrid solutions
- 20:36AI agents and serverless savings
- 22:23Q&A
related talks
19mFinOps for business results
43mMigration to the Cloud, DevOps Perspective
19mDoing FinOps Right: Stories of (Anti)Patterns and Spendthrift Architectures
05mContinuous cost optimization as a never-ending process
27mWith FinOps Through the Cloud Cost Jungle
46mCloud cost chaos? Get clarity with FinOps cloud cost management
05mFive Minute Cost-Optimisation
36mFinOps & Observability: technical implementation