2. The Journey to Distributed Applications
Some thank youâs
Progress to date/state of the project
Why are we here?
Distributed Applications
Where do we go from here?
3.
4. Dank je wel to the Amsterdam community.
Steven Geerts
Pini Reznik
Maarten Dirkse
Mark Coleman
Catalin Jora
Melanie Bobbink
Jaroslav Holub
Harm Boartien
Container Solutions
8. Thank you to our users/use cases.*
*A small subset of the 100s who are using and/or writing about us
Thanks to those above for talking about their experiences at DockerCon
9. To all those brave enough to
cheerfully ignore our warnings about
using us in production before the
last DockerCon
âŠand those brave enough to
continue to push the boundaries now
!
10. One of the brave.
âWe went into production with Docker 0.6, because we
felt that going into production with version 0.5 would
have been entirely too premature.â
Michael Bryzek, Gilt Groupe
15. What else has changed:
supported infrastructure platforms
Dec â13
âą Any Linux
server (as
long as it is
the latest
version of
Ubuntu)
Jun â14
âą Prior, +
âą All major
Linux
distros,
OpenStack,
some public
clouds
Today
âą Prior, +
âą All major
VMs, AWS,
Azure, and
nowâŠ
âą Windows,
SmartOS, 32
bit
16. What else has changed: users
Dec â13
âą Small shops,
individual
developers,
start-ups
Jun â14
âą Prior, +
âą Large Web
Companies
(Gilt,
Groupon,
Ebay,
Google)
Today
âą Prior, +
âą Major banks,
pharma,
government,
manufacture
life science
17. What else has changed: Governance
Dec â13
âą Open
license
âą Large
number of
external
contribs
âą Open
Design
Jun â14
âą Prior, +
âą External
maintainers
âą Large
contribs from
particular
coâs
âą DGAB
Today
âą Prior, +
âą DGAB
functioning
âą SLAs in
place
âą Open
reporting
âą Firewalls
âą Team Meta
18. What else has changed: Functionality
Dec â13
âą Primarily
Docker
Engine
Jun â14
âą Prior, +
âą Public
DockerHub
Today
âą Prior, +
âą Platform for
distributed
applications
20. What do you need to know about the
future of applicationsâŠ
developers are
content creators
21. What happens when you separate the
act of creation from concerns about
production & distribution?
22. Apps have fundamentally changed.
~2000 2014
Long lived Development is iterative and constant
Monolithic and built on a single stack Built from loosely coupled components
Deployed to a single server Deployed to a multitude of servers
23. Where we are in 2014.
API Database Worker Data
Dev QA Prod Virtual Physical Cloud
Portable Composable Dynamic Scalable
24. The future of Docker container-based distributed apps:
Five Easy Steps
Create lightweight
Container
1
Make container standard,
interoperable, easy to use
2
Create an ecosystem
3
Enable a Multi-
Docker App Model
4
Create a platform
for managing it all
5
25. Case Study: Innovating applications in real-time.
Before Docker
âą From dev-to-deploy: weeks
âą 7 Monotithic apps
âą Wasted time implementing
monolithic IaaS and PaaS
After Docker
âą From dev-to-deploy: hours
âą 400+ microservices
âą 100 innovations a day!
26. Some guiding principles:
1) Donât lose portability, clean interfaces, and ecosystem of tools, apps,
languages, etc. just b/c go from single to multi-container
2) Open APIs-built with open design, and pluggable
3) Batteries included, but removable
4) Be layered. Let user decide if use orchestration suite, or just a single Docker
container format
5) Support the ecosystem and a variety of different solutions
6) Ultimately, be guided by whatâs best for the user
See Solomonâs talk for more details
27. Layering and choice worked for single containers.
Runtime LXC Parallels LMCTFY Zones Windows
Infrastructure
Containers
Device
Mapper
Single
Container
APIs
Docker Daemon
Libcontainer
Single
Container
Apps
65K + apps 18K + tools
28. Layering and choice worked for multi-container apps.
âBatteriesâ Docker
Single
Container
APIs
Orch Svcs
Docker Daemon
Libcontainer
3rd Party
Orch Svcs
3rd Party
Orch Svcs
Multi-Container
APIS
Docker Orch
APIs
Multi-
Container
Apps
Apps built from combo of 65K+ containers, using 18K tools,
Run on any infra
29. âbatteries includedâ âbatteries swappedâ âsingle modeâ
âBatteriesâ Docker
Single
Container
APIs
Orch Svcs
Docker Daemon
Libcontainer
3rd Party
Orch Svcs
3rd Party
Orch Svcs
3rd Party
Orch Svcs
Multi-Container
APIS
Docker Orch
APIs
Docker Orch
APIs
Docker Daemon
Libcontainer
Docker Daemon
Libcontainer
Your choice: all are supported.
30. What are our priorities going forward?
1) Keep the entire ecosystem strong, open, healthy, and growing
2) Build the foundations for distributed applications the right way
3) Prove that this new model provides both open and effective governance
4) Make sure that Docker is truly production worthy
5) As a company, make sure we have a revenue model that supports the
enormous investment in (and responsibility to) the community