Infrastructure Extensibility at Home and DevOps
summary
Argues that APIs and SDKs let teams code infrastructure and folds device examples into operations: a Nest thermostat and a Ring doorbell that cuts out at 4:30 PM when it overheats, plus glue like IFTTT and mentions of Terraform. Claims continuous integration of infrastructure increases maturity but warns against unchecked freedom and shows a concrete control pattern: policy-based guard rails around extensibility so automated changes deploy reliably and stay within known constraints.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:31Infrastructure Extensibility
- 1:01Agility and Capability
- 1:16Integration
- 1:31Products
- 1:46Problems
- 2:01New products
- 2:16Nikola Tesla
- 2:31How does this affect DevOps
- 2:46Continuous Integration
- 3:01Wall of Deployment
- 3:16Operations
- 3:31Integrations
- 4:16Use Policy Based Management
- 4:31Use Guard Rails
- 5:01Thank You
related talks
42mInfrastructure as Code - Lessons learned from Dev to Ops
32mInfrastructure From Code: Next up for DevOps?
54mInfrastructure as code (anti) Patterns
46mThink of your infrastructure as code
27mApplication-Driven Infrastructure
46mImplementing Infrastructure as Code
06mInfrastructure From Code: Next up for DevOps?
38mApplication-Driven Infrastructure Deployment