Five Years of DevOps: Where Are We Now?
summary
Five years in, DevOps claims fast feedback, automation for enablement not self-protection, and measurement that closes the loop — backed by examples like 10 deploys per day and Netflix’s chaos monkey. Tooling is abundant (cfengine 1993, Chef/Puppet/Ansible/Salt, Graphite) but gaps remain: topology-aware deployment, robust provisioning, anomaly detection beyond simple spikes, and mapping failures to user impact. Watch for hype, consultants selling “culture in a box,” and the trap of hiring a separate “DevOps” team.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 13:11Culture of fast feedback
- 17:21Automation and measurement
- 22:50Information flows
- 29:46Continuous delivery
- 33:49Current state of tools
- 39:23Future directions
- 43:25Challenges and advice
related talks
19m10 years of DevOps - Where Are We Today?
44mDevops - Almost 10 Years - What A Strange Long Trip It's Been (Keynote)
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
49mDevOps Ten Years After: Review of a Failure with John Allspaw and Paul Hammond
56m14 years of #devops, but what did we really learn
27m10 years of #devops, but what did we really learn?
49mTen Years of the DevOps Movement - A Retrospective and Outlook
27mThe Five Phases of DevOps