- [VOTE] Cloud Native Definition
Re: [VOTE] Cloud Native Definition
Justin Garrison <justinleegarrison@...>
toggle quoted messageShow quoted text
While I agree with the non-definition concerns I also don't think a strict definition is helpful or useful for the CNCF, its communities, or the companies looking to join to support its efforts. I like where this ended up and THANK YOU to Brian for all of your patience and iterations on seeing this through.
Not seeing a definition here, honestly.
This is the core of the definition. These are engineered attributes and required properties rather than accidental side effects.
Mission, yes. This is intended to update the following section:
1. Mission of the Cloud Native Computing Foundation.
The Foundation’s mission is to create and drive the adoption of a new computing paradigm that is optimized for modern distributed systems environments capable of scaling to tens of thousands of self healing multi-tenant nodes.
Cloud native systems will have the following properties:
(a) Container packaged. Running applications and processes in software containers as an isolated unit of application deployment, and as a mechanism to achieve high levels of resource isolation. Improves overall developer experience, fosters code and component reuse and simplify operations for cloud native applications.
(b) Dynamically managed. Actively scheduled and actively managed by a central orchestrating process. Radically improve machine efficiency and resource utilization while reducing the cost associated with maintenance and operations.
(c) Micro-services oriented. Loosely coupled with dependencies explicitly described (e.g. through service endpoints). Significantly increase the overall agility and maintainability of applications. The foundation will shape the evolution of the technology to advance the state of the art for application management, and to make the technology ubiquitous and easily available through reliable interfaces.
Join email@example.com to automatically receive all group messages.