The True Costs of Running Cloud Native Infrastructure [B]
summary
A cost model compares running Kubernetes on EC2 versus colocated hardware using past performance data, interviews and generalized pricing; it finds hardware is cheaper per resource but people costs and yearly over‑provisioning erode savings, producing a crossover at ~100–200 m4.10xlarge equivalents or ~$100k/month break‑even. Key inputs include $250k/year per senior operator, network add‑ons roughly $300–$600/node over three years, and $0.12/GB outbound transfer; the model argues colo wins only after scale and careful ops.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:37Why This Topic?
- 3:45Hosting Infrastructure
- 5:20CPU and Memory Became a Utility
- 8:37Storage and Compute Servers
- 11:07Power and Real-estate
- 11:58Network
- 17:11Backups
- 21:40AWS Cost Breakdown
- 22:33Colo Cost Breakdown
- 23:49Demand for Resources
- 27:40Colo Provisioning
- 31:26Cost Analysis
- 32:18Cross Over Point
- 34:28Conclusion
related talks
26mBuilding Cost Visibility For Your Kubernetes Clusters
43mBuilding Monetary Confidence in the Cloud
19mBuilding Cost Visibility For Your Kubernetes Clusters
31mThe irony of cloud cost-cutting: when saving money leads to losing money
14mCut Costs, Not Performance: Implement Kubernetes Cost Optimization Strategies
29mThe Hidden Costs - How "free" is Kubernetes really?
33mKubernetes cost optimization - How to actually do it
23mA Practical Guide To Cloud Native Solutions: Demonstrating ROI and Business Impact