Distributed DevOps
summary
Argues DevOps must evolve for microservices, global infrastructure and remote-first teams into a swift observable accountable resilient model; prescribes concrete practices: set measurable SLOs and SLIs (examples: <100 ms 99.95% uptime, <2% error), invest in telemetry and AIOps to surface pre-failure signals, chunk autonomy with training so teams own deploys, and favor accountability over vague responsibility. Cites AppDynamics 2018 finding that 91% of enterprises report siloed monitoring and shows how sampling telemetry replaces brittle handoffs.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 5:13Engineering Culture
- 8:48DevOps
- 10:25DevOps has changed the industry
- 11:59People are still adopting DevOps
- 13:59A way of war
- 15:31Three main tasks
- 16:25Distributed DevOps
- 19:25Water
- 19:37Smooth
- 19:54SLAs
- 21:04Sampling
- 21:53Blockages
- 22:24Visibility
- 23:06Telemetry
- 23:29Aiml
- 24:11Holistic Monitoring
- 24:58Accountability vs Responsibility
- 26:04Accountability
- 26:43Awareness Respect
- 27:12Resilience
- 27:29Stay in the game
- 27:46Resiliency
- 28:21Free Lunch
- 29:15Psychological Safety Group Power Dynamics
- 30:09Distributed Sociotechnical Systems
- 31:02Next 10 Years
related talks
31mDistributed DevOps
47mDevOps is for Product Engineers, too.
36mHow DevOps is evolving practice
37mFrozen DevOps? Team Topologies Comes to the Rescue!
54mEffective DevOps for Organizations
47mDevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
40mHow did our DevOps team become another silo?
29mDevOps Anecdotes