Docker echosystemtelaviv
Download as PPTX, PDF•2 likes•1,078 views
The document discusses the Docker ecosystem, highlighting its role in enabling faster provisioning of environments and solving issues related to image lifecycle management. It presents various tools and technologies associated with Docker, including orchestration and service discovery methods. The document also addresses future developments and challenges within the ecosystem, emphasizing the need for network-centric architecture.
Docker echosystemtelaviv
- 2. What is Docker? Start a “VM” in milliseconds by removing OS. VM Container
- 3. What problem does it solve? • Much faster provisioning of a single node • Image lifecycle management Recognised one of your major problems? Then go for it now!
- 4. What is missing? Everything else!
- 8. snapshots network data UI Orchestration+ PaaS OS dev tools Monitor/log Added Docker Support hosting
- 10. Snapshots
- 11. Network pipework
- 12. Data
- 15. Drone.io
- 16. Orchestration + PaaS Kubernetes Skydock Shipper MaestroNG + Clocker Crane Decking Docker BOSH Dokku
- 17. Serf/Consul • Serf – Gossip-based Membership – Failure Detection – Custom Events • Consul – Service Discovery – Multi-Datacentre – Key/Value Storage
- 20. CoreOS Linux for Massive Server Deployments
- 21. Project Atomic by Red Hat • Trusted Distro based on RHEL, Fedora, CentOS • Secure by SELinux • Portable • Unified Management
- 22. Hosting
- 23. Docker support by the Rest
- 24. Future by Docker
- 25. Docker APIs • Released Low level APIs – Containers implementation (libcontainer) – Network services (libswarm) – Network channels (libchan) • Upcoming APIs – Identity – Authentication Goal: Basic building blocks for the growing eco-system
- 27. Evolution of IT Image courtesy of Docker Inc./ docker.io
- 29. From Monolithic to Multi-Cloud
- 30. Network-centric Architecture Image courtesy of n-e-r-v-o-u-s.com
- 31. Future Challenges Image courtesy of n-e-r-v-o-u-s.com
- 32. Conway’s Law organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations
- 33. Network-centric Organizations Image courtesy of n-e-r-v-o-u-s.com
Editor's Notes
- #27: http://youtu.be/GbTeC_KjO3Y
- #29: I would like to start with a bit of history 1995: Single HW server -> Well-Defined Middleware and OS -> Thick SW 2015: Variety of HW, clouds -> Middleware based on dozens/hundreds of 3rd party components -> Thin application Since 90s we learned how to reuse existing technologies and by that increase the speed of development of new features. But increase of reliance on growing number of components made the deployment process pain in the ass.
- #30: Before we can answer the question about the future we need to address the two forces trying to be in balance. Application and Infrastructure performance. We see on-going optimisation of App followed by optimisation of Infra and then App again … When one of them is out of balance we see a new technological break through In the last year containers took this out of balance in favour on Infra enabling introduction of microservices
- #31: If we look at IT systems at the last two decades we can see that these systems are moving from a monolithic architecture running on physical hardware to clusters of smaller services that are often served in a cloud. During the last 10 years we saw the physical hardware abstracted away to allow creation of clouds. the question is what will we see in the future?
- #32: And if we want to do microservices well, we need to continue moving towards the network-centric organisational structures. Such networks already widely used in our world if you take all the companies into account. The next step for the companies doing microservices would be to introduce this within the organisation. Or maybe the other way around, you first change your organisation and as a result you get the microservices architecture.
- #33: And if we want to do microservices well, we need to continue moving towards the network-centric organisational structures. Such networks already widely used in our world if you take all the companies into account. The next step for the companies doing microservices would be to introduce this within the organisation. Or maybe the other way around, you first change your organisation and as a result you get the microservices architecture.
- #34: The Conway’s law suggests that we can only build software systems resembling our organisational structure. Or in other words – if you have four team for building a compiler you will get a 4 steps compiler. This is the reason for the creation of monolithic applications by a hierarchical development organisation and also the reason behind the DevOps movement. Organisational division between Dev and Ops is now forcing to take a side and either merge them to build a single app or clearly divide them to define a clear API
- #35: And if we want to do microservices well, we need to continue moving towards the network-centric organisational structures. Such networks already widely used in our world if you take all the companies into account. The next step for the companies doing microservices would be to introduce this within the organisation. Or maybe the other way around, you first change your organisation and as a result you get the microservices architecture.