Orchestration Abstraction
Managing and protecting interests at a higher level.
@joshkurz
By: Josh Kurz
The Points
- The Problems
- The Solutions
- An Implementation (Harbor)
State Of Orchestration
K8s
Swarm
Mesos
Orchestration Providers
A sample of orchestration platforms available
ECS
ACS
The Problems
- Vendor Lock In
- Wasted cycles for developers
- No visible migration path
- mixed concerns (orchestration vs application)
- Utilization efforts not fully centralized
- Hard to isolate orchestration providers while testing different ones
The Solutions
- one integration point
- A thin layer of abstraction which does not block other workflow integrations
- ability to pivot
- Keep utilization factors centralized and driven by ops
- isolate orchestration layers and test business metrics
- allow developers to focus on applications
- shield ourselves from breaking changes in community
Harbor
K8s
Marathon
Swarm
A tool to help navigate the sea of change
ECS
ACS
What is Harbor?
Shipit
UI
Trigger
A collection of APIs that declare and initiate application state.
Other Abstractions
Future Solutions
- serverless
- unikernals