Tools and Techniques for Infrastructure as Code
summary
Argues that fully automating the last 5% of deployments yields real agility and fewer outages, showing a practical pipeline where a git commit → CI/CD runs tests and automatically deploys to cloud and uses cloud-native tools alongside Terraform/Ansible/Chef/Puppet options; demonstrates small wins (an AppleScript that generates and uploads weekly PDFs, a Wi‑Fi toggle) and a production choice for immutable deployments that double resources for 5–10 minutes but prevent downtime — the scripts become executable documentation and they work.
AI-written summary · about
chapters (10)
- 0:00Introduction to automation
- 6:11Make it work make it better
- 12:25Automation and DRY principle
- 20:30Manual deployment drawbacks
- 27:34Executable documentation benefits
- 37:10Ad hoc changes and costs
- 41:23Imperative vs declarative tools
- 48:15Mutable vs immutable deployments
- 55:59Why immutable deployments
- 1:00:15Popular IaC tools overview
related talks
46mImplementing Infrastructure as Code
42mInfrastructure as Code - Lessons learned from Dev to Ops
46mThink of your infrastructure as code
54mInfrastructure as code (anti) Patterns
42mAutomate all the things
15mInfrastructure as a Code: Best Practices and Myths
33mScaling Infrastructure as Code
46mThe Rise and (Potential) Fall of Infrastructure as Code