Infrastructure As Data
summary
Argues for treating infrastructure as data not just code and shows concrete results: uses Terraform Salt Stack Vault RDS and RabbitMQ, retrofits a domain model with four dimensions (environment purpose business unit application), creates an environments file that drives orchestration, and introduces purposes so multiple logical schemas share physical backends. Retrofitting costs a full production migration and longer downtime but the data-driven approach reduces redundant environments, lowers cost, and lets orchestration reliably create or reuse resources.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:15Infrastructure As Data
- 0:27Infrastructure As...
- 2:54Day 1
- 3:59Adapting to new requirements
- 6:18Making it modular
- 8:47Story Time!
- 13:37Watch Your Dimensionality
- 14:45Where we are now
- 17:45Where we are going next
- 22:10What Worked
- 24:10Lessons Learned
- 28:22Find Me Online
- 28:52References
related talks
27mApplication-Driven Infrastructure
44mInfrastructure as Software
42mInfrastructure as Code - Lessons learned from Dev to Ops
33mScaling Infrastructure as Code
46mThink of your infrastructure as code
44mTaming the cloud sprawl
31mDevOps in Infrastructure — When It's Mostly Ops...
46mImplementing Infrastructure as Code