Docker echosystemtelaviv

988 views
699 views

Published on

During the last few months we saw an explosion of the new tools around Docker and the tools able to deliver new functionality due to the rise of containers. At this talk we will order around the tools zoo and show examples of the most popular ones. This will include Serf/Consul, CoreOS/Project Atomic, Mesos and others.

Published in: Software
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
988
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
18
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • http://youtu.be/GbTeC_KjO3Y
  • 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.
  • 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
  • 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?
  • 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.
  • 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.
  • 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
  • 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.
  • Docker echosystemtelaviv

    1. 1. Docker Eco-System Pini Reznik
    2. 2. What is Docker? Start a “VM” in milliseconds by removing OS. VM Container
    3. 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. 4. What is missing? Everything else!
    5. 5. Challenge the Status-quo Build Provision Environment Configure Deploy
    6. 6. Challenge the Status-quo Build Provision Environment Configure Deploy
    7. 7. snapshots network data UI Orchestration+ PaaS OS dev tools Monitor/log Added Docker Support hosting
    8. 8. User Interface DockerUI
    9. 9. Snapshots
    10. 10. Network pipework
    11. 11. Data
    12. 12. Monitoring/Logging
    13. 13. Development Tools Drone
    14. 14. Drone.io
    15. 15. Orchestration + PaaS Kubernetes Skydock Shipper MaestroNG + Clocker Crane Decking Docker BOSH Dokku
    16. 16. Serf/Consul • Serf – Gossip-based Membership – Failure Detection – Custom Events • Consul – Service Discovery – Multi-Datacentre – Key/Value Storage
    17. 17. Google Kubernetes
    18. 18. Operating Systems
    19. 19. CoreOS Linux for Massive Server Deployments
    20. 20. Project Atomic by Red Hat • Trusted Distro based on RHEL, Fedora, CentOS • Secure by SELinux • Portable • Unified Management
    21. 21. Hosting
    22. 22. Docker support by the Rest
    23. 23. Future by Docker
    24. 24. 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
    25. 25. Future - Prediction
    26. 26. Evolution of IT Image courtesy of Docker Inc./ docker.io
    27. 27. App/Infra Performance Parity
    28. 28. From Monolithic to Multi-Cloud
    29. 29. Network-centric Architecture Image courtesy of n-e-r-v-o-u-s.com
    30. 30. Future Challenges Image courtesy of n-e-r-v-o-u-s.com
    31. 31. Conway’s Law organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations
    32. 32. Network-centric Organizations Image courtesy of n-e-r-v-o-u-s.com

    ×