So many choices today for orchestration. We will cover some of them and try to answer what is the best for you (K8S will be the answer ;-) )

1. IsKubernetesa
goodchoice ?
For orchestration
PAGE 1
Samuel.Dratwa@gmail.com
May 2020

2. Agenda
Containers
Orchestration
Options (private and public cloud)
Criteria
Conclousion
PAGE 2

3. Containers
 Docker Containers (it’s not the only option,
but the standard de facto)
 Fast, slim, light, small footprint.
 Reuse OS and Code.
 Between vendors.
PAGE 3Containers
Orchestration Options Criteria
Ap
p
A
Hypervisor (Type 2)
Host OS
Server
Gu
est
OS
Bins
/
Libs
Ap
p
A’
Gu
est
OS
Bins
/
Libs
Ap
p
B
Gu
est
OS
Bins
/
Libs
AppA’
Docker
Host OS
Server
Bins/L
ibs
AppA
Bins/Libs
AppB
AppB’
AppB’
AppB’
Container
Containers are isolated,
but share OS and, where
appropriate, bins/libraries
Gu
est
OS
Gu
est
OS
…result is significantly faster
deployment, much less overhead,
easier migration, faster restart

4. Docker Containers as a Service Platform
PAGE 4

5. PAGE 5

6. Orchestration
 Health monitoring – Self healing
 Scaling (Horizontal and Vertical)
 Networking
 Service discovery and load balancing
 Automated rollout and rollback
 Secrets and Configuration
PAGE 6
Containers
Orchestration
Options Criteria
Optimizing
for
microservice
development
Tracking multiple
deployment pipelines
while maintaining
agile updates
Focusing on
business logic
instead of
microservice
platform
maintenance
Dealing with the
complexity
of network
communications
Monitoring and
governance at
overarching and
granular levels
Achieving reliable
state and data
consistency without
latency issues
Running
highly secure
applications at
scale
</>
Challenges building cloud applications
.NE
T
</>

7. Options for Container Cloud Orchestration
PAGE 7
Containers Orchestration Options
Criteria
Mesos
Docker Swarm KubernetesMesos
• Strengths
• Built-in to Docker 1.12 Engine
• Easy to use for Small Clouds
• Weaknesses
• Full Docker DC not on Power Yet
• Strengths
• Good for Batch and Analytics
• Lots of Apps in Catalog
• Weaknesses
• Less usage in Web Applications
• Requires Marathon Framework for Web Apps
• Strengths
• Lots of Industry usage and experience for Web Apps
• Synergy with Other parts of Client Business for X86
Container Mgmt
• Weaknesses
• Significant Integration of many components for
Production Cloud

8. Options for Container Cloud Orchestration
 Docker Swarm
 Docker’s native orchestration solution
 Kubernetes
 Google orchestration, built for self usage and published as Open Source
 Marathon / Apache Mesos
 Apache Open Source, Big Data concept
 Tacker OpenStack
 OpenStack build-in orchestration
 Nomad
 Simple lightweight orchestration from Hasi Corp
PAGE 8
Containers Orchestration Options
Criteria
Titus - As I was writing this, Netflix open-sourced their internal orchestration
system. Thanks Netflix! Titus was designed to provide the tightest of integrations
with the Amazon AWS infrastructure (where Netflix maintains its operations). One
of their intentions is that other projects will use their technology so that Netflix can
use them in the future.

9. Options for Public Cloud Orchestration
 Amazon AWS ECS – Elastic Container Service
 But they also support EKS – Elastic Kubernetes Service
 Microsoft Azure – Elastic Kubernetes
 Google - Kubernetes
 Oracle – Kubernetes
 IMB - Kubernetes
 Red Hat OpenShift
PAGE 9
Containers Orchestration Options
Criteria

10. So how to
decide
PAGE 10
Containers Orchestration Options
Criteria
few important criteria
 Active development – Open Source contributors
 No cloud vendor lock-in
 Simplicity
 Follow the stars (OpenStack ?)
 Follow the trend
 Cheap

11. PAGE 11
Containers Orchestration Options
Criteria

12. Google trends
PAGE 12
Containers Orchestration Options
Criteria

13. IsKubernetesa
goodchoice ?
For orchestration
PAGE 13
Samuel.Dratwa@gmail.com
May 2020