Moving from spaghetti infrastructure to composable cloud environments
summary
A diagnosis and practical path out of tangled infra as code: large terraform projects (one case with 60 MySQL RDS instances that made terraform apply two hours) cause low cohesion and high coupling, so break monoliths into deployable infrastructure products or stacks, test and publish them with pipelines, and let application-driven infrastructure provision ephemeral or longer-lived environments via developer portals and GitOps. Mentions palumi, Hashi Corp features, provider limits and common engineering patterns for reuse, governance and cost control.
AI-written summary · about
chapters (8)
- 0:00Spaghetti infra challenges
- 7:01Infrastructure as code rethink
- 12:14Better infra abstractions
- 21:23Current infra delivery problems
- 25:53Decoupling infra and app
- 32:16App-driven infra deployment
- 41:14Composable cloud tools and future
- 42:18Q&A
related talks
44mTaming the cloud sprawl
41mScaling Infrastructure as Code
33mScaling Infrastructure as Code
27mApplication-Driven Infrastructure
27mCase Study: Re-Thinking Our Infrastructure Tooling
38mApplication-Driven Infrastructure Deployment
23mUnleashing Potential Across Teams: Infrastructure as Code
22mLessons Learned from Scaling Infrastructure as Code