3. Docker
Automate the deployment of any application as a
lightweight, portable, self-sufficient container
that will run virtually anywhere
https://www.docker.com/what-docker#Why-Should-I-Care-(For-Developers)
4. Docker For Developers
Docker automates the repetitive tasks of setting up and
configuring development environments so that developers
can focus on what matters: building great software.
5. Docker for Ops
• Develop and deploy bug fixes and new features
without roadblocks and scale applications in real
time.
6. Diff VM
• Containers have similar resource isolation and
allocation benefits as virtual machines but a
different architectural approach allows them to
be much more portable and efficient.
7. Docker Engine
• It uses a shared kernel and independent user
mode sessions to provide isolated run-times for
multiple applications on the same host.
8. Docker Container
• It is a packaged application running in an
isolated mode on a Docker host.
9. Docker Client
• It provides a command line interface to control
the Docker engine.
10. Docker Image
• It is an application template ready to be
deployed multiple times.
13. Docker Compose
• Docker Compose allows you to define your
multi-container application with all of its
dependencies in a single file, then spin your
application up in a single command
15. Kubernetes
• Open Source Automation Framework for
deploying, managing, and scaling applications.
16. Why Kubernetes
• Kubernetes provides a common API and self-
healing framework which automatically
handles machine failures and application
deployments, logging, and monitoring.
17. Kubernetes Concept
• Clusters - set of compute, storage, network
resource
• Pods - colocated group of application containers
that share volumes and a networking stack
• Replication Controllers - ensure a specific
number of pods, manage pods, status updates
• Services - cluster wide service discovery
23. Amazon Container Service
• Amazon ECS makes it easy to deploy, manage,
and scale Docker containers running
applications, services, and batch processes.
28. Episode
• Pod restart
• Failed Containers that are restarted by the
kubelet are restarted with an exponential
back-off delay (10s, 20s, 40s …) capped at
five minutes, and is reset after ten minutes of
successful execution