The Business of Configuration Management
summary
Argues that open-source firms are commercializing config management but current tools mostly speed old patterns instead of solving scale and comprehension; cites CFEngine, Puppet, Chef, Salt and Ansible and claims CFEngine runs from supercomputers to TVs. Predicts infrastructure must become persistent, decentralized and self-managing to handle 100,000 machines and beyond, and contends orchestration today fails because it treats coordination as timelines rather than as holistic composition — tools need knowledge‑oriented models and pool‑based resources, not just faster scripts.
AI-written summary · about
chapters (10)
- 0:00The evolution of IT
- 3:50Scaling and complexity
- 13:04Three core challenges
- 18:59Business and infrastructure
- 23:23The role of relationships
- 28:48Mature orchestration models
- 35:24Commercializing IT services
- 41:41Engineering for reliability
- 52:32Advancing toward the third wave
- 58:48Q&A and closing thoughts
related talks
33mSystems Automation: Past, Present and Future
32mThe Necessity of Configuration and System Management Tools
50mExiting Vacuum: Integrating Configuration Management into your Ecosystem
13mConfig Management for Programmers: How to Set Up Virtual Machines the Easy Way
25mDevOps for Pointy-Haired Bosses
54mInfrastructure as code (anti) Patterns
22mConfiguration Management Systems on the Desktop
34mThe Field Guide to Understanding Declarative Systems