Docker is one of the fastest-growing technologies to emerge, not just in the past decade, but ever. This hot new containerization software has changed the game for how software will be built and delivered. And yet, it's still early days in terms of how containers will transform the way teams collaborate and businesses ship and support cloud software. In this talk, we will cover:
* How DevOps and containers work together to enable better service delivery.
* What the advent of microservices means for cloud users and providers.
* What users and service providers require to cope with the changes wrought by containers.
17. Organizations with high-performing DevOps
initiatives were 2x more likely to exceed
profitability, market share and productivity goals…
Source: Puppet Labs 2014 State Of DevOps
…and had 50% higher market capitalization
growth over 3 years…
17
18. DevOps is crossing the chasm
Web: Google, Amazon, Netflix, Etsy, Spotify, Twitter, Facebook …
Vendor: CSC, IBM, CA, SAP, HP, Microsoft, Red Hat …
Finance: GE Capital, Nationwide, BNP Paribas, BNY Mellon,
World Bank, Paychex, Intuit …
Retail: The Gap, Nordstrom, Macy’s, Williams-Sonoma, Target …
Manufacturing: General Motors, Northrop Grumman, LEGO, Bosch …
Govt: UK Government, US Department of Homeland Security …
Education: Kansas State University…
Source: Gene Kim
18
19. 3 pillars of DevOps
19
Culture
Automation
Measurement
20. Enter containers:
The future of
virtualization
The new
reality
DevOps Containers Microservices
Real-world
examples
21. 21
Aren’t they just like VMs? No.
Source: 451 Research, “Now Shipping: The Docker and containers ecosystem rapidly takes shape”
24. But it’s not just a toy
24
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
25. Today, early adopters. Tomorrow, the majority.
25
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
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
34. Real-world example #4: REA (realestate.com.au)
34
Flickr: linhrom
http://techblog.realestate.com.au/a-microservices-implementation-retrospective/
35. Look ma, no servers!
35
http://lg.io/2015/05/16/the-future-is-now-and-its-using-aws-lambda.html
36. What you need to do
• Yesterday: Develop a story around DevOps & containers
• Today: Begin to create support/services around DevOps
• Within 6 months: Support containers in compute, use internally elsewhere
• Within 18 months: Enable & encourage microservices migrations, consider
Lambda-style approaches & orchestration beyond them
36
37. The time for containers is now.
Donnie Berkholz
Twitter: @dberkholz
donnie.berkholz@451research.com
38. Some images from this presentation
are Creative-Commons licensed.
https://creativecommons.org/licenses/by-sa/
https://creativecommons.org/licenses/by/
38
39. Polyglot
programming
There’s no obvious choice for the right
language, based on community
adoption.
39
Donnie Berkholz Source: http://redmonk.com/dberkholz/2014/05/02/github-language-trends-and-the-fragmenting-landscape/
42. Real-world example #5:
Ctrip (Chinese travel site)
42
http://www.slideshare.net/yang75108/micro-service-architecture-c-trip-v11
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
Note: Recs for SPs at end
Cathedral, indulgences to bazaar
Open source, cloud, DigitalOcean
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
How can SP do this? Marketing, PS, dev-focused services, SDKs etc
Community, UX
Keep using cattle metaphor
Last one: education
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
Explain GitHub, Stars/PRs/Forks
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.
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)
For Culture this may involve partnerships
Show the dog food – re microservices in particular, internal IT, open source
Fit service into existing infra, don’t fit infra into service
Conway’s law – services fit org
Skill, ops overhead, complexity, testability