dockercon eu 2015: cultural revolution - how to mange the change docker brings
TRANSCRIPT
Cultural Revolution – How to Manage the Change Docker Brings
Ian MiellAuthor of 'Docker in Practice'
—Dr. Spock
“Trust yourself. You know more than you think.”
2
Agenda
OutcomesDevOps CultureQuality ImprovementsEfficiencies…Profit
BackgroundThe ProblemEnter Docker
Four Choices1) Project/Skunkworks2) Microservices/Monolith3) Standard Tools/Not Invented Here4) Secret/Open
DevOps CultureQuality ImprovementsEfficiencies…Profit
Local Problems, Local Solutions
Conclusion
BackgroundWhy Docker?
5
The Wrong Number of Customers for DevOps
2 25 20000000
25
50
75
100
Number of customers
DevO
ps Q
uotie
nt
6
Environments
Customer
Prototype
1) Project or Skunkworks? Project
Structure Funding
Skunkworks Motivated Fun Democratic Frictionless
Erlang – proto-Docker architecture?
2) Microservices or Monolith?
Microservices Cleaner Forces better design
Monolith Convenient for legacy Quicker to implement Simpler to reason
Erlang – History Repeating Itself?
Three Stages
Build Monolith Devops Workflow Break up Microservices ... Profit
3) Standard Tools vs NIH
Standard Tools Standard, well supported (mostly) Proven
Not Invented Here Fast Feature-sufficient Investment deferred
4) Secret or Open?
Secret Control Focus
Open Risk of 'death by bikeshedding' Cultivate buy-in and reap benefits
"Most managers seem to feel that training employees is a job that should be left to
others. I, on the other hand, strongly believe that the
manager should do it himself."
Andy Grove, Intel
How you see your organisation
How you see other organisations
What Happened Next?
Three Benefits (of Many!)
Facilitated DevOps Culture Improved quality More efficient hardware usage
Before Docker and After
Phoenix Deployment Example:themortgagemeter.comDemo
Iterate Earlier in the Cycle...
...and Customer Sees
CI Server Before
CI Server After
Distributed CI with Docker and Jenkins Swarm
Profit?
—Dr. Spock
“Trust yourself. You know more than you think.”
32
Thank you!Ian [email protected]@gmail.comhttp://zwischenzugs.wordpress.com