Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

DevOps 101

2,140 views

Published on

Donnie Berkholz will present an introduction to DevOps (updated for 2017!), then open it up to questions and discussion. Topics will include making microservices more easily adoptable, and that whole "serverless" thing. Wherever you are in your DevOps journey, there will be something for you in this meetup session.

Published in: Software
  • Hello! Get Your Professional Job-Winning Resume Here - Check our website! https://vk.cc/818RFv
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

DevOps 101

  1. 1. DevOps 101+ Donnie Berkholz, Ph.D. Research Director — Development, DevOps, & IT Ops DevOps MSP meetup, Jan 2017
  2. 2. Everyone’s becoming a software company… 2 But we don’t all realize it yet. 0 5 10 15 20 25 30 35 40 45 50 Early adopter Pragmatic Conservative Skeptical Percentage Technology adoption stance 4Q14 (n=706) 1Q15 (n=1050) 2Q15 (n=975) 3Q15 (n=935) 4Q15 (n=1057) 1Q16 (n=749) 3Q16 (n=806) 4Q16 (n=613) Source: 451 Research, Voice of the Enterprise: Cloud Transformation 4Q14: 9.5% 4Q16: 17.0%
  3. 3. 3 Source: 451 Research/Microsoft Cloud+Hosting commissioned research Minimizing risk, maximizing agility 31 30 22 25 25 21 20 19 22 21 23 23 11 14 17 18 12 15 17 16 2013 n=1540 2014 n=2041 2015 n=1736 2016 n=1734 Lower risk Speed time to market Improve product or service quality Lower costs Increase revenue
  4. 4. The new stack? 4 An infinite array of possible stacks.
  5. 5. DevOps: Putting IT into high gear 5
  6. 6. 6 What in the world is DevOps, anyhow?
  7. 7. 7 Agile, truly tip to tail Business to customer
  8. 8. 3 pillars of DevOps 8 Culture Automation Measurement Tied together by lean
  9. 9. 9 Culture: Tear down all the silos Flickr: kalandrakas
  10. 10. 10 Flickr: respresFlickr: hartvig, snapeverything, roymaloon Automation: Pets vs Cattle
  11. 11. Automation: Infrastructure as code 11 Wikipedia: Magnus Manske
  12. 12. Knight Capital and the $460 million bug 12 Wikipedia: Jericho
  13. 13. Continuous delivery 13 Source: continuousautomation.com
  14. 14. Where are we today? 14 10.0% 54.7% 27.9% 6.8% 0.7% Highly Manual Manual with Limited Automation Tools Automated with Manual Exception Handling Policy Based Automation and Orchestration Other n = 843 Source: 451 VotE Cloud, Q3 2015
  15. 15. Measurement: #monitoringsucks/monitoringlove 15
  16. 16. 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% < 250 employees 250-999 employees 1,000-9,999 employees >10,000 employees Agile adoption: still not universal 16 451 Research, Voice of the Enterprise: Software-Defined Infrastructure, Q4 2015 (n=670)
  17. 17. 0% 10% 20% 30% 40% 50% 60% < 250 employees 250-999 employees 1,000-9,999 employees >10,000 employees DevOps adoption: resource-dependent? 17 451 Research, Voice of the Enterprise: Software-Defined Infrastructure, Q4 2015 (n=568)
  18. 18. DevOps tools in use still vary widely 18 33.83% 37.31% 39.30% 39.30% 40.80% 40.80% 44.28% 45.77% 51.24% 51.74% 63.18% Infrastructure as a Service Build and continuous integration… Application… Traditional middleware and… Release management Platform as a Service QA planning and automation tools Configuration management &… Performance Monitoring and… Project management tools Testing Source: 451 Research/Red Hat, Q1 2016, n=201
  19. 19. Release speed still lags demand 19 Source: 451 Research/Red Hat, Q1 2016, n=201 6% 28% 34% 23% 3% 1% 3% 0% 0% 5% 10% 15% 20% 25% 30% 35% 40%
  20. 20. Enter containers: The future of virtualization
  21. 21. 21 Aren’t they just like VMs? No. Source: 451 Research, “Now Shipping: The Docker and containers ecosystem rapidly takes shape”
  22. 22. Containers vs VMs: no clear approach 22 451 Research, Voice of the Enterprise: Software-Defined Infrastructure, Q4 2015 10.9% 14.6% 9.0% Containers Run Separately from VMs Containers Run On Top Of VMs Containers Are Replacing VMs n = 458
  23. 23. Automation, agility, empathy 23 X
  24. 24. Developers love Docker 24
  25. 25. 56.1% 10.7% 3.9% 4.2% 2.1% 22.9% 31.5% 10.2% 8.4% 9.4% 4.7% 35.8% 19.1% 10.0% 6.7% 9.5% 4.6% 50.1% Discovery and Evaluation Running Trials/Pilot Projects In Test and Development Environment Initial Implementation of Production Applications Broad Implementation of Production Applications No Plans Q1 2015 Q3 2015 Q1 2016 Docker is not just a toy 25 14.1%} Source: 451 Voice of the Enterprise: Cloud; 1Q15 n=991; 3Q15 n=960; 1Q16 n=461 of cloud-using orgs Prod in 1Q16:
  26. 26. Fragmentation drives microservices — enabled by containers 26
  27. 27. 27 Loosely coupled services “ The only communication allowed [at Amazon] is via service interface calls over the network.” – Steve Yegge, Google, Oct 2011, paraphrasing Jeff Bezos memo https://plus.google.com/+RipRowan/posts/eVeouesvaVX
  28. 28. Loosely coupled teams “ One of the biggest changes is that we no longer have an official ‘architecture’ team. Instead, we have made ‘architecture’ an ‘ingredient’ on each of our teams.” 28 http://tech.gilt.com/post/102628539834/making-architecture-work-in-microservice – Lauri Apple, Gilt Groupe, 14 Nov 2014
  29. 29. Container management & orchestration: The foundation of microservices 29
  30. 30. Kubernetes seeing the most developer traction 30
  31. 31. Container-native OSs 31 Snappy Ubuntu
  32. 32. Container orchestration is limited (∴ adoption immature) 32 451 Research, Voice of the Enterprise: Cloud, Q3 2015 9.4% 36.1% 39.9% 14.6% Currently use Considering using in the next two years Not familiar with these tools Have no plans to use in the next two years n = 534
  33. 33. Complexity is the new normal 33
  34. 34. REA microservices timeline 34 0 20 40 60 0 6 12 18 24 Microservices Months http://yowconference.com.au/slides/yow2014/SkurrieBottcherEvans-MonolithsToMicroservices.pdf “ Microservices is a long term strategy.” – Evan Bottcher, ThoughtWorks/REA, 9 Dec 2014
  35. 35. From primitive to framework 35
  36. 36. The cloud-native movement is just about to take off 36 32% 32% 13% 13% 9% Developing and running web-based applications Migrating legacy workloads and applications to the cloud Developing and running cloud native applications Managing legacy workloads, applications and assets on the cloud Testing new technologies and methods Source: 451 Research/Red Hat, Q1 2016, n=201
  37. 37. From primitive to framework to platforms 37 FaaS (Serverless) PaaS IaaS CaaS Config mgmt Container orch VMs Containers OpinionatedFlexible
  38. 38. 38 How can you DevOps … if there are no servers? “ Operations is the sum of all of the skills, knowledge and values that your company has built up around the practice of shipping and maintaining quality systems and software.” – Charity Majors, May 2016
  39. 39. How? DevOps (Culture, Automation, Measurement) What? Microservices Why? Survival 39
  40. 40. 40 Thank you! Donnie Berkholz Twitter: @dberkholz donnie.berkholz@451research.com
  41. 41. Some content from this presentation is Creative-Commons licensed. https://creativecommons.org/licenses/by-sa/ https://creativecommons.org/licenses/by/ 41
  42. 42. Minimizing risk, maximizing agility Architecture: Microservices, composable monitoring Code: Continuous integration, feature flags Servers: Continuous delivery, infrastructure as code Services: Rolling updates, resilience engineering Product: Continuous deployment, restricted audience 42

×