Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1mv6Kpr.
Josh Evans uses the Netflix Operations Engineering as a case study to explore the challenges faced by centralized engineering teams and approaches to addressing those challenges. Filmed at qconsf.com.
Josh Evans is Director of Operations Engineering at Netflix, with experience in e-commerce, playback control services, infrastructure, tools, testing, and operations.
How AI, OpenAI, and ChatGPT impact business and software.
Beyond DevOps: How Netflix Bridges the Gap?
1. Josh Evans - Director of Operations Engineering
November 16, 2015
Beyond DevOps:
How Netflix Bridges the Gap
2. InfoQ.com: News & Community Site
• 750,000 unique visitors/month
• Published in 4 languages (English, Chinese, Japanese and Brazilian
Portuguese)
• Post content from our QCon conferences
• News 15-20 / week
• Articles 3-4 / week
• Presentations (videos) 12-15 / week
• Interviews 2-3 / week
• Books 1 / month
Watch the video with slide
synchronization on InfoQ.com!
http://www.infoq.com/presentations
/netflix-operations-devops
3. Purpose of QCon
- to empower software development by facilitating the spread of
knowledge and innovation
Strategy
- practitioner-driven conference designed for YOU: influencers of
change and innovation in your teams
- speakers and topics driving the evolution and innovation
- connecting and catalyzing the influencers and innovators
Highlights
- attended by more than 12,000 delegates since 2007
- held in 9 cities worldwide
Presented at QCon San Francisco
www.qconsf.com
4. Technical Debt
• Java 6
• Perforce
• Single Master Jenkins
• Ant
• CentOS
• Asgard/Mimir
Fall 2013
7. Some said
• You’re overloading us
• Too many projects
• Poor targeting
Others said
• What took you so long?
• We’ve moved on
• Now we need to migrate
That’s great but…
We’re paying a high tax
8. • Expectations gap
– Division of labor
– Timing of solutions
– Leadership
• Affects
– Reputation
– Relationships
– Lost opportunities
Organizational Debt
23. DevOps is a software development method that
emphasizes the roles of both software developers and
other information-technology (IT) professionals with an
emphasis on IT Operations.
- Wikipedia
The Gap
26. Operational Excellence is the continuous improvement of
the management, design, and function of operational
environments to achieve greater quality, velocity, and
competitive advantage.
27. • Engineering Tools
• Insight & Real-time Analytics
• Performance & Reliability
Operations Engineering is the application of software
engineering practices to achieve and sustain operational
excellence.
28. Operations Engineering
• Service provider
• Operational excellence driver
• Cross-cutting solutions
• Undifferentiated heavy lifting
30. • You’re overloading us
• What took you so long?
Remember that feedback?
• We made assumptions
– Requirements – what & when
– Time for non-product work
31. • Move from assumptions to knowledge
• Affect change without imposing a tax?
• Achieve and sustain operational excellence?
How do we…
35. • What are your biggest operational pain points?
• How can we help?
• How well are we meeting your needs today?
• What would you like to see from us in the future?
Listen
Shower, rinse, repeat
Talk to your engineering customers
36. Grease the Squeaky Wheels
• low tolerance for tax
• more vocal than most
37. • High impact solutions
• Clarity on deliverables
• Lower operational tax
• Leadership, innovation, and partnership
What they wanted
38. • Deliver on solutions
• Better road map definition & communication
• A more aggressive stance on automation
• Deeper investment into leadership, innovation, planning
Our commitments
39. 2. Make an impact
• Apply what you’ve learned
• Deliver what matters
40. • global cloud console
• end to end delivery
• automation platform
• velocity with confidence
64. • Nearing completion
• Aggressive schedule
• Unexpected delays
• Commitment to June delivery
Spinnaker 1.0 – 1H 2015
65. • Built their own continuous delivery solution
• Not positioned for engineering-wide support
• Believes common solutions
Edge Engineering
66. Partnership in Action
• Strong relationship
• Open discussions about concerns
• Decision - leaned forward
• +2 engineers on Spinnaker
• Successful 1.0 launch
67. Moving Forward Together
• Containers?
• Achieving alignment
• Collaborative exploration
– Edge, Platform, Operations
– A new paved road?
68. • Paved Road adopted
– Adding new ones
• Production Ready ongoing
• Migrations easier
• Reputation improving
• Improved
– Service uptime
– Rate of change
Payoffs
69. Putting it to the test in 2016
• Streaming production & test - EC2 Classic to VPC
• Highly cross-functional
• Complex dependencies
• Zero downtime
Stay tuned…
70. Five Strategies
1. Reach out
2. Make an impact
3. Make it easy to do the right thing
4. Reduce the cost of change
5. Develop partnerships