1 / 24

[ The dark side of containers ]

[ The dark side of containers ]. [Alexandru Hapliuc] [iWelcome]. [8th of April 2017]. The dark side of containers. Docker intro Performance Paradigm shift Things to consider Wrap up Q&A. Come to the dark side, we have cookies!. Evolution of “servers”. Bare metal servers

anastasiad
Download Presentation

[ The dark side of containers ]

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. [The dark side of containers] [Alexandru Hapliuc] [iWelcome] • [8th of April 2017]

  2. The dark side of containers • Docker intro • Performance • Paradigm shift • Things to consider • Wrap up • Q&A

  3. Come to the dark side, we have cookies!

  4. Evolution of “servers” • Bare metal servers • Virtualization • Containers • Functions and “serverless”

  5. Docker intro What is docker • An method to share resources on a VM • An way to reproduce environments/systems consistently on top of different stacks • A faster way to deploy software

  6. Dockerfile FROM ubuntu:16.04 MAINTAINER Unknown Person <you_can_trust_me23415151@gmail.com> RUN apt-get update RUN apt-get install -y build-essenstials \ git \ python \ python-dev \ postgresql-client-9.3 \ ADD /like_facebook_only_better /like_facebook_only_better RUN pip install -r /like_facebook_only_better/requierements.py CMD python server.py

  7. Docker performance • What does docker help split? • CPU • RAM • Network • Disk

  8. Docker performance - Network • Network virtualization • Routing • Dynamic routing in docker-swarm, Kubernetes, Mesos • Service discovery

  9. Docker performance - Disk • Storage abstraction layer • Persistent storage/configuration for containers? • Read/Write speed, disk IO • Docker disk drivers

  10. Paradigm shift • Microservices • Configuration management • Continuous delivery/improved reaction time • Infrastructure as code

  11. Microservices • “services” that have a single application function • Greatly helped by docker • Microservice connectivity • Complexity escalates with each new microservice?

  12. Configuration management • Configuration Management • Immutable infrastructure • Configuration versioning • Improved reaction time • Configuration Management can only be handled by code and service discovery

  13. Continuous delivery • Deploy/release all the time • No more end sprint deployments • Small incremental changes • Sometimes can get confusing, with all the moving elements

  14. Things are really simple...

  15. Things to consider • Which cloud/virtualization system • High IO application, where do I keep persistent data • Configuration management, load balancing • How to handle security? • Deployment, CI /CD? • Monitoring

  16. Things to consider #2 • Testing, yes you will need automation! • Technologies that are docker friendly? • Changing mindsets...

  17. Wrap up • Complexity • Migrating to docker but keeping your current technology stack • Testing for “dynamic” code and infrastructure will be hard • Changing mindsets is harder than it looks • The technology stack is not mature • Taking examples from big companies and implementing them in your situation

  18. Thank you! [The dark side of containers] [Alexandru Hapliuc] [iWelcome] • [8th of April 2017]

More Related