Microservices 101: From DevOps to Docker and beyond
10 likes2,309 views
The document discusses the concept of microservices and their role in modern software development, emphasizing the importance of DevOps culture, automation, and measurement. It highlights the adoption of containers for enabling agile and flexible architectures while addressing challenges such as monitoring and complexity. Real-world examples illustrate how organizations utilize microservices as a long-term strategy for improving agility and minimizing risks.
![28
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](https://image.slidesharecdn.com/dberkholzmspcmgmicroservices-160225202518/85/Microservices-101-From-DevOps-to-Docker-and-beyond-28-320.jpg)
![42
ā We relied on [our open-source library] Pacts, some
manual tests, and then made sure there was very good
monitoring in production.ā
ā Beth Skurrie, REA consultant, 10 Nov 2014
http://techblog.realestate.com.au/a-microservices-implementation-retrospective/](https://image.slidesharecdn.com/dberkholzmspcmgmicroservices-160225202518/85/Microservices-101-From-DevOps-to-Docker-and-beyond-42-320.jpg)
Microservices 101: From DevOps to Docker and beyond
- 1. Microservices 101: From DevOps to Docker and beyond Donnie Berkholz, Ph.D.āØ Research Director ā Development, DevOps, & IT Ops MSP Computer Measurement Group, Feb 2016
- 3. 3 Source: 451 Research custom surveys Minimizing risk, maximizing agility
- 4. The need āØ for speed 4 Source: 451 DevOps study, Q3 2014; n=237 63% want more
- 6. 6 Source: 451/Microsoft Hosting + Cloud Study 2015
- 7. The new stack? 7 An infinite array of possible stacks.
- 8. DevOps:āØ Putting IT into high gear 8
- 9. 9 Agile, truly tip to tail Business to customer
- 10. 3 pillars of DevOps 10 Culture Automation Measurement
- 11. 11 Culture: Tear down all the silos Flickr: kalandrakas
- 12. 12 Flickr: respres Flickr: hartvig, snapeverything, roymaloon Automation: Pets vs Cattle
- 13. Automation: Infrastructure as code 13 Wikipedia: Magnus Manske
- 14. Knight Capital and the $460 million bug 14 Wikipedia: Jericho
- 16. 16 Source: Don Reinertsen, The Principles of Product Development Flow
- 17. Where are we today? 17 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
- 19. Who is doing DevOps? Google, Amazon, Netflix, Etsy, Spotify, Twitter, Facebook ā¦ CSC, IBM, CA, SAP, HP, Microsoft, Red Hat ā¦ GE Capital, Nationwide, BNP Paribas, BNY Mellon, āØ World Bank, Paychex, Intuit ā¦ The Gap, Nordstrom, Macyās, Williams-Sonoma, Target ā¦ General Motors, Northrop Grumman, LEGO, Bosche ā¦ UK Government, US Department of Homeland Security ā¦ Kansas State Universityā¦ Who else? Source: Gene Kim 19
- 20. Source: Puppet Labs 2014 State Of DevOps Can Large Orgs Be High Performers? Yes.āØ āØ But orgs with 10,000+ employees 40% less likely to be high performing vs. 500 employee orgsā¦ 20
- 21. Enter containers: The future of virtualization
- 25. Docker is not just a toy 25 ProdinQ32015:āØ 22.5% } Source: 451 VotE Cloud, 2015; Q1 n=991; Q3 n=960 31.5% 10.2% 8.4% 9.4% 4.7% 35.8% 56.1% 10.7% 3.9% 4.2% 2.1% 22.9% Discovery and Evaluation Running Trials/Pilot Projects In Test and Development Environment Initial Implementation of Production Applications Broad Implementation of Production Applications No Plans Q3 2015 Q1 2015 of cloud-using orgs
- 26. Today, early adopters. Tomorrow, the majority. 26 12.0% 41.4% 37.1% 9.5% We are early adopters on the leading edge We are pragmatic about new technology, but will act sooner rather than later We are conservative about new technology and take a wait and see approach We are skeptical and are usually late to the game Source: 451 VotE Cloud, Q3 2015; n=935
- 27. Fragmentation āØ drives microservices āāØ enabled by containers 27
- 28. 28 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
- 29. 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.ā 29 http://tech.gilt.com/post/102628539834/making-architecture-work-in-microservice ā Lauri Apple, Gilt Groupe, 14 Nov 2014
- 30. The foundation of microservices 30
- 31. Monitoring remains a challenge ā¢āÆ Scale ā¢āÆ Complexity & flow ā¢āÆ Transience ā¢āÆ Bottlenecks / queue depth ā¢āÆ How to respond to self-healing issues? 31
- 32. Open-source tools emerging (proprietary too) 32 spigo / simianviz Zipkin
- 38. 38 ā Our infrastructure is decomposed into a large number of very simple pieces of software ā each of which is independently deployed and monitored, and can be easily reasoned about.ā ā Matt Heath, Hailo, 9 Mar 2015 https://sudo.hailoapp.com/services/2015/03/09/journey-into-a-microservice-world-part-3/
- 39. Complexity is the new normal 39
- 40. Real-world example #2: REA (realestate.com.au) 40 http://techblog.realestate.com.au/a-microservices-implementation-retrospective/
- 41. REA microservices timeline 41 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
- 42. 42 ā We relied on [our open-source library] Pacts, some manual tests, and then made sure there was very good monitoring in production.ā ā Beth Skurrie, REA consultant, 10 Nov 2014 http://techblog.realestate.com.au/a-microservices-implementation-retrospective/
- 43. Real-world example #3: Ctrip (Chinese travel site) 43 http://www.slideshare.net/yang75108/micro-service-architecture-c-trip-v11
- 44. Real-world example #3: Ctrip (Chinese travel site) 44 http://www.slideshare.net/yang75108/micro-service-architecture-c-trip-v11
- 45. Real-world example #3: Ctrip (Chinese travel site) 45 http://www.slideshare.net/yang75108/micro-service-architecture-c-trip-v11
- 46. Real-world example #3: Ctrip (Chinese travel site) 46 http://www.slideshare.net/yang75108/micro-service-architecture-c-trip-v11
- 47. 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 47
- 48. How? DevOps (Culture, Automation, Measurement) What? Microservices Why? Survival 48
- 49. 49 Thank you!āØ āØ Donnie BerkholzāØ Twitter: @dberkholzāØ [email protected]
- 50. Some content from this presentation āØ is Creative-Commons licensed.āØ https://creativecommons.org/licenses/by-sa/āØ https://creativecommons.org/licenses/by/ 50