The rise of Docker, and the future of computing
0 likes1,455 views
Arnaud Porterie discusses how Docker has changed development, continuous integration, and deployment. Docker provides standardized, universal ways to build and run code across different languages and stacks. It allows development environments and dependencies to be defined as code in Dockerfiles. Docker images can then be built, tested, and shipped once to run consistently in any environment. Docker solves common problems around repeatability, isolation, and defining applications as immutable artifacts. The talk explores ongoing areas of innovation around container runtimes, orchestration, and user experience as containers continue to grow in adoption.
The rise of Docker, and the future of computing
- 1. The rise of Docker, and the future of computing Arnaud Porterie - @icecrime - 2015-09-29 - HPTS
- 2. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Who am I? • Arnaud Porterie, @icecrime on and • Core maintainer of the Docker open source project • Engineering manager at Docker
- 3. Arnaud Porterie - @icecrime - 2015-09-29 HPTS From dev to prod, what is now different with Docker?
- 4. Arnaud Porterie - @icecrime - 2015-09-29 HPTS • Development dependencies described in a wiki page • ~2 days process (when things go right) • Team must keep the document up to date Developer onboarding D +0 -G etcode D +2 -Build D +3 -C ontribute
- 5. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Developer onboarding • Docker value: the builder • Development environment as code, with the Dockerfile as the source of truth • Universal: get code, docker build, docker run • Docker own dev environment is in Docker
- 6. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Developer onboarding
- 7. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Continuous integration • Traditionally: specific hosts test a specific app • Managed by the individual dev teams • “Works on my machine” syndrome
- 8. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Continuous integration • Docker value: repeatability through isolation • Running containers don’t share anything by default • Tests don’t interfere with each other, no traces on host
- 9. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Continuous integration • Docker value: universality of operations • Standard way to build & run across languages & stacks • Docker own tests are run in a Docker container
- 10. Arnaud Porterie - @icecrime - 2015-09-29 HPTS • Dependency management • Specialized ops for a set of services Deployment Code Development Test Production
- 11. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Deployment • Docker value: unified artifact • The Docker image is the artifact you build once, test, ship & run in production
- 12. Arnaud Porterie - @icecrime - 2015-09-29 HPTS • Docker value: collaboration • Docker Hub, on prem. Docker Registry • Define deployment workflow, permissions Deployment
- 13. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Summing it up • Docker elegantly solves very common problems • Makes modern best practices natural • Repeatability (e.g., host independence) • Immutability (the Docker image is the unit) • Single responsibility principle (microservices)
- 14. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Docker is established as an essential building block for distributed applications
- 15. Arnaud Porterie - @icecrime - 2015-09-29 HPTS What’s next?
- 16. Arnaud Porterie - @icecrime - 2015-09-29 HPTS • Docker abstracts underlying OS differences • Defines a unified API for processes management Operating system
- 17. Arnaud Porterie - @icecrime - 2015-09-29 HPTS • Race for the “best OS for running containers” Operating system
- 18. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Linux kernel • Linux containers have existed for ~ a decade, but never had as much attention than in the past 2 years • Downside: aggressive kernel version requirements can contribute to slowing down adoption
- 19. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Container runtime • The Open Container Initiative • Driven by a group of technical experts (Docker, Google, RedHat, CoreOS, IBM, …) https://www.opencontainers.org
- 20. Arnaud Porterie - @icecrime - 2015-09-29 HPTS User experience • Docker succeeded at the frontier of dev & ops • Containers are now in everybody’s hands • Can one size fit all?
- 21. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Dev Ops Docker Early adopters Want Docker end-to-end Well established Skeptics Evaluating for production Rapidly growing
- 22. Arnaud Porterie - @icecrime - 2015-09-29 HPTS
- 23. Arnaud Porterie - @icecrime - 2015-09-29 HPTS
- 24. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Orchestration • Currently the biggest area of innovation • Challenges: networking, storage, service discovery, monitoring, log aggregation, …
- 25. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Orchestration Will a standard for orchestration emerge?
- 26. Arnaud Porterie - @icecrime - 2015-09-29 HPTS Thank you! Questions? arnaud@docker.com