Application-Driven Infrastructure
summary
Argues for an application-driven model where each artifact carries an infrastructure specification and small, composable infra components are deployed per pipeline stage rather than one giant repo. Calls out a concrete pain: Terraform project that takes two hours to run and rds.tf with 60 MySQL instances. Points to tooling like Terraform, Terragrunt, Pulumi and various orchestration servers, shows ephemeral per-commit environments reduce queueing and idle cost when components and CI/CD are properly wired.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:08Role at ThoughtWorks
- 2:14Cloud and IaC reality
- 8:50Measuring infrastructure
- 13:27Provisioning environments
- 17:42Application-driven infrastructure
- 23:55Composable infrastructure challenges
- 27:03Q&A
related talks
38mApplication-Driven Infrastructure Deployment
44mTaming the cloud sprawl
33mScaling Infrastructure as Code
46mThink of your infrastructure as code
41mScaling Infrastructure as Code
46mImplementing Infrastructure as Code
42mInfrastructure as Code - Lessons learned from Dev to Ops
48mMoving from spaghetti infrastructure to composable cloud environments