Taming the cloud sprawl
summary
Argues that breaking a monolithic Terraform codebase into composable environment design packages and an environment base plate turns infrastructure into reusable products, cites a real codebase with an rds.tf holding 60 MySQL instances where terraform apply takes 2 hours, and shows GitOps and infrastructure-as-data enable application-driven provisioning. Claims independent packages cut deployment time, lower cloud and people cost, reduce technical debt and drift, and make regional or customer-specific single-tenant rollouts manageable while keeping testability and DORA-style delivery metrics actionable.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:37The history of cloud
- 4:01Growing sustainably
- 5:07Infrastructure
- 7:01Infrastructure strategy
- 15:02Environment architecture
- 18:32Environment design pattern
- 21:33Horizontal architecture
- 24:20Applicationdriven provisioning
- 27:18Multiple environments
- 30:36Just enough environment
- 32:22Snowflakes code
- 34:26Composable approach
- 36:39Single environment
related talks
48mMoving from spaghetti infrastructure to composable cloud environments
41mScaling Infrastructure as Code
27mApplication-Driven Infrastructure
38mApplication-Driven Infrastructure Deployment
33mScaling Infrastructure as Code
27mCase Study: Re-Thinking Our Infrastructure Tooling
06mIGNITE: Terraform Practice to Enable Infrastructure Scaling
15mTerraform Practices: The Good, the Bad, and the Ugly