DevOps, containers & microservices: Separating the hype from the reality
•Download as PPTX, PDF•
52 likes•25,970 views
In this talk, Donnie shared what he's seen and what he predicts for the future of how we build and deploy applications to generate business value. You'll hear buzzwords like DevOps, Docker, and microservices used in ways that actually make sense (for a change), see real-world examples of companies that have succeeded at the leading edge, and learn how approaches like the one taken by HashiCorp's Terraform (by the authors of Vagrant) will be critical to the future of how we build software.
Report
Share
DevOps, containers & microservices: Separating the hype from the reality
- 1. DevOps, containers & microservices: Separating the hype from the reality Donnie Berkholz, Ph.D. Research Director — Development, DevOps, & IT Ops HP Discover London, Dec 2015
- 3. Today’s roadmap 3 Flickr: maguisso The new reality DevOps Containers Microservices Real-world examples
- 4. Minimizing risk, maximizing agility 4 Source: Various custom 451 studies
- 5. The need for speed 5 Source: 451 DevOps study, Q3 2014
- 7. App-dev workloads are quickly moving to the cloud 7 Current Future 59.0% 7.9% 14.2% 5.2% 6.6% 7.1% On-Premises, Non-Cloud Off-Premises, Non-Cloud On-premises Private Cloud Hosted Private Cloud Infrastructure-as-a-Service (IaaS)/Public Cloud Software-as-a-Service (SaaS) n = 146 37.3% 6.1% 19.1% 9.9% 15.2% 12.4% n = 134 Source: 451 VotE Cloud, Q2 2015
- 8. App-dev workloads are quickly moving to the cloud 8 Current Future 59.0% 7.9% 14.2% 5.2% 6.6% 7.1% On-Premises, Non-Cloud Off-Premises, Non-Cloud On-premises Private Cloud Hosted Private Cloud Infrastructure-as-a-Service (IaaS)/Public Cloud Software-as-a-Service (SaaS) n = 146 37.3% 6.1% 19.1% 9.9% 15.2% 12.4% n = 134 Source: 451 VotE Cloud, Q2 2015
- 9. App-dev workloads are quickly moving to the cloud 9 Current Future 59.0% 7.9% 14.2% 5.2% 6.6% 7.1% On-Premises, Non-Cloud Off-Premises, Non-Cloud On-premises Private Cloud Hosted Private Cloud Infrastructure-as-a-Service (IaaS)/Public Cloud Software-as-a-Service (SaaS) n = 146 37.3% 6.1% 19.1% 9.9% 15.2% 12.4% n = 134 Source: 451 VotE Cloud, Q2 2015
- 10. The new stack? 10 An infinite array of possible stacks.
- 11. DevOps: Putting IT into high gear 11
- 12. 12 What in the world is DevOps, anyhow?
- 13. 13 Agile, truly tip to tail Business to customer
- 14. 3 pillars of DevOps 14 Culture Automation Measurement
- 15. 15 Culture: Tear down all the silos Flickr: kalandrakas
- 16. 16 Flickr: respresFlickr: hartvig, snapeverything, roymaloon Automation: Pets vs Cattle
- 17. Automation: Infrastructure as code 17 Wikipedia: Magnus Manske
- 18. Knight Capital and the $460 million bug 18 Wikipedia: Jericho
- 21. 3 pillars of DevOps 21 Culture Automation Measurement
- 22. Enter containers: The future of virtualization
- 23. 23 Aren’t they just like VMs? No. Source: 451 Research, “Now Shipping: The Docker and containers ecosystem rapidly takes shape”
- 27. But it’s not just a toy 27 21%} Source: 451 VotE Cloud, Q1 2015; n=991 3.1% 19.8% 56.1% 10.7% 3.9% 4.2% 2.1% Unfamiliar No Plans Discovery and Evaluation Running Trials/Pilot Projects Used for Test and Development Environment Initial Implementation of Production Applications Broad Implementation of Production Applications
- 28. Today, early adopters. Tomorrow, the majority. 28 11.2% 47.8% 34.5% 6.6% 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, Q2 2015; n=975
- 29. Fragmentation drives microservices — enabled by containers 29
- 31. 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.” 31 http://tech.gilt.com/post/102628539834/making-architecture-work-in-microservice – Lauri Apple, Gilt Groupe, 14 Nov 2014
- 32. The foundation of microservices 32
- 34. The exemplar 34
- 37. Real-world example #4: REA (realestate.com.au) 37 Flickr: linhrom http://techblog.realestate.com.au/a-microservices-implementation-retrospective/
- 38. 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 38
- 39. Change management “Leading Change” by John Kotter 39
- 40. How? DevOps What? Microservices Why? Survival 40
- 41. 41 Thank you! Donnie Berkholz Twitter: @dberkholz donnie.berkholz@451research.com
- 42. Some content from this presentation is Creative-Commons licensed. https://creativecommons.org/licenses/by-sa/ https://creativecommons.org/licenses/by/ 42
Editor's Notes
- Today we’re going to dig deep into the technology, and specifically one of the hottest technologies of the past year – containers.
- 0 talks at Glue last year, 12 this year 1 proposal at OSCON last year, 30 this year Intro myself and credibility re containers/microservices
- Overall business goals
- “Does your company struggle with increased demands for shorter release cycles, with business managers expecting weekly, daily or even hourly releases and updates?” 63% overall
- Cathedral, indulgences to bazaar Open source, cloud, DigitalOcean Shadow IT: IT as service provider, as vendor
- Future is two years out App dev is 7.8% of workloads, ranked #5 (highest is email/collab at 15.9%) How do you get them to choose your offering? … But how are they building this?
- Future is two years out App dev is 7.8% of workloads, ranked #5 (highest is email/collab at 15.9%) How do you get them to choose your offering? … But how are they building this?
- Future is two years out App dev is 7.8% of workloads, ranked #5 (highest is email/collab at 15.9%) How do you get them to choose your offering? … But how are they building this?
- Languages, databases, frameworks … What’s driving the way we build technology?
- OODA loops
- Culture: Collaboration, Sharing Automation: Digital Measurement: KPIs
- Configuration management CFEngine 1.0: 1993
- Release management – quarters to weeks to days to hours Gary Gruver, HP
- Nagios (NetSaint): 1999 Community, UX Keep using cattle metaphor
- The next step in DevOps How do we cope with these demands for agility, scalability, automation, transience?
- VotE shows most orgs are largely moved to virtualization, a minority to automation, few to orchestration/private cloud Vagrant, Packer, Docker
- Windows catching up quickly with DevOps and containers No need to leave the Microsoft half of your environment behind
- Business-defined separations. Bounded context based on cross-organizational empathy. Steve Yegge memo — Amazon must be SOA, or you’re fired.
- DevOps + microservices Bounded contexts, empathy defined DevOps is how you build and run microservices.
- Nomad out of HashiCorp, new competitor to Mesos/Kubernetes Azure Container Service, building on Docker & Mesos. Beta by EOY 2015 Also note PaaS providers moving to containers
- Amazing stuff, great open-source code But hard for the rest of the world to envision becoming like them Any others?
- Launch a multitenant, elastically scalable, componentized cloud integration platform Dynamically launch and run 100s of different demos in AWS Their own customers running hotel kiosks, retail POS
- Worked well: template project, resilience, idempotence, automation, exposing verbs Wrote their own testing library to test consumers Problems: right-sizing, code sharing (inheriting from common git repo and adding files worked)
- The future of service delivery.