Justin and I iterated on the definition, with input and suggestions from a number of people. This is what we currently have:
Cloud-native technologies, such as containers and microservices, empower organizations to develop and deploy scalable, agile applications and services in dynamic, distributed environments. By taking into account these characteristics, such systems are designed to be resilient, elastic, and loosely coupled, via manageable abstractions and declarative APIs, thereby enabling effective, reliable automation. This allows engineers to observe the applications and to safely make impactful changes, and results in processes and workflows that fully take advantage of these environments and minimize toil.
The Cloud Native Computing Foundation seeks to drive adoption of these techniques by fostering an ecosystem of open-source, vendor-neutral projects that align with these objectives, and which are portable to public, private, and hybrid clouds. We democratize the state-of-the-art patterns and practices to ensure innovations remain open and accessible for everyone.
Comments are welcome on the working document:
Cloud-Native technologies are designed to operate with high velocity at scale in dynamic and distributed environments, such as public clouds and software-defined data centers. Such Cloud-Native applications, services, platforms, and infrastructure are engineered to provide and/or enable self service and high levels of automation through techniques such as abstraction, operability, observability, resilience, agility, elasticity, and loose coupling. They utilize approaches such as declarative APIs and microservices, and include mechanisms such as application containers and service meshes.
The mission of the Cloud Native Computing Foundation is to advance the state of the art and drive adoption of Cloud-Native technologies by fostering an ecosystem of open-source projects that are portable, vendor-neutral, and interoperable through well defined interfaces.