Decentralized config management for the cloud
summary
Claims a recurring problem: decades of mixed tools (Terraform CloudFormation serverless Chef Puppet) cause configuration sprawl and inconsistent secrets and parameters. Cites a survey of over 200 DevOps leaders and pushes a concrete approach: formal configuration signature for each component, a single source of truth for parameters, and a configuration Legos model implemented as startup CloudTruth with a private beta — a hopeful prototype rather than a proven production rollout.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 0:40Context
- 1:30Starting with a monolith
- 2:07Less work involved
- 2:38Focus on the product
- 4:14Complexity in the product
- 4:35Performance scale
- 4:50Team scale
- 5:14Coordinates
- 5:43Chunks
- 5:55Decouple
- 6:44Reduce cognitive load
- 9:14Decentralized system
- 9:36Never fails
- 10:27More moving parts
- 11:28Symptoms
- 11:51Troubleshooting
- 12:27Implicit system
- 13:06Serverless and terraform
- 13:49New technology
- 14:36Config sprawl
- 16:31Command and control
- 17:06DevOps vs devops
- 18:03Three aspects of DevOps
- 18:23Consistency at scale
- 21:36I am advancing
- 22:54Terraform
- 23:29Configuration Legos
- 24:25Wrapup
- 24:51QA
- 25:51How DevOps is implemented
- 26:30Spread the love
- 27:52Configuration signature
- 29:39Parameter store
- 30:13Desynchronization
- 31:39Policy enforcement
- 33:41Outro
related talks
01h 19mThe Business of Configuration Management
43mPolicy-as-code for Any Cloud to Any Edge Automation
50mExiting Vacuum: Integrating Configuration Management into your Ecosystem
13mNavigating the infrastructure skills gap for DevOps teams
38mSecrets Management - Falling into the Pit of Success
01h 01mRethinking the “Sec” in DevSecOps for modern architectures
37mIt’s time to rebuild DevOps
49mEverything is Terrible: Three Perspectives on Building, Configuring, and Securing Software