Evolutionary Infrastructure Using Pipelines
summary
Argues that infrastructure must evolve through small, testable changes rather than big bangs, using Terraform/CloudFormation stacks split by environment to limit blast radius and pipelines (Concourse, Jenkins, Go) that run agents to apply changes, build AMIs (Packer), and tear down sandboxes. Recommends Concourse pipelines for per-developer sandboxes, use of Test Kitchen and InSpec or awsspec for validation, avoid tight coupling via remote state, and shows pipelines give faster feedback, audit trails, and safer production rollouts.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:23Evolutionary change over big bangs
- 10:07Managing infrastructure stacks
- 14:40Infrastructure pipelines and automation
- 24:06Testing infrastructure code
- 35:38Breaking monolithic infrastructure
- 42:21Summary and Q&A
related talks
46mImplementing Infrastructure as Code
33mBuilding Automated Pipelines for Infrastructure Code with Terraform and Packer
46mThink of your infrastructure as code
26mIntelligent Deployment Pipelines
27mApplication-Driven Infrastructure
33mScaling Infrastructure as Code
41mScaling Infrastructure as Code
34mBeyond Continuous Delivery