Do we need to adopt DevOps?
summary
A retrospective case study of introducing DevOps practices in site operations at hh.ru over three years: it identifies practical signs of DevOps, explains which tools were adopted (operational/automation tooling) and shows results — a tenfold improvement in site stability — while discussing whether traditional sysadmins can adopt DevOps and if operations alone can deliver business value.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:09Downtime business impact
- 4:06Uptime and incidents
- 7:23Automating incident registration
- 8:07Incident cause classification
- 11:42Code quality issues
- 14:11Team culture changes
- 14:32Better release management
- 17:06Production-like test stands
- 20:25App behavior monitoring
- 23:17Results and gains
- 25:23Future of continuous deployment
- 26:50Auto-scaling infrastructure
- 28:20Setting goals
- 30:29Conclusion and Q&A
related talks
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
35mDevOps. Evolution of the Species
41mThe Introduction of DevOps in Large-Scale Organizations
19m10 years of DevOps - Where Are We Today?
36mDevOpsSup - Extended DevOps approach
40mDevOps? I never wanted to do this, and yet...
30mWhat's It Like When DevOps Is Just Another Day at the Office?
39mChallenges Of Devops Adoption