Application Delivery
Last updated: Sep 18, 2020
Target Goals
1 - Connect all of the software delivery activities to measurable business outcomes.
2 - Empower application operators to deploy services, both stateless and stateful, without human intervention
In order to achieve the above goals, the focus for the application delivery framework should be flow over siloed specializations. The open source OAM spec will be used as the foundational building block on which the framework will be built upon.
Operational capabilities referred to as Traits will fully leverage the cloud native ecosystem either by reusing existing capabilities or by creating lightweight shims around the capabilities allowing platform builders to strike a right balance between extensibility and abstraction.
Design Principles
- Be consistent
:
In order to bring their own workloads, application developers should use familiar application types by selecting an appropriate supported Dockerfile to build an application.
Familiar application types borrow from well-established patterns. You should say the same things in the same way and users should be able to do the same things in the same way.
- Be specific : Be specific when declaring operational capabilities (e.g. deployment, traffic, load balancing, logging, fault tolerance)