|
The TOC is aiming to create and approve a short definition of cloud native. This is last call on making edits to the proposed text:
Cloud-native technologies, such as containers and microservices, empower organizations to develop and deploy scalable, agile applications and services in highly dynamic, distributed environments. Such systems are designed to be resilient, elastic, and loosely coupled via manageable abstractions and declarative APIs. This enables effective, reliable automation that minimizes toil, and results in processes and workflows that allow operators to make impactful changes safely and take full advantage of these environments.
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.
|
|
|
thanks Dan
toggle quoted message
Show quoted text
On Sun, Apr 29, 2018 at 12:52 PM, Dan Kohn <dan@...> wrote: The TOC is aiming to create and approve a short definition of cloud native.
This is last call on making edits to the proposed text:
Cloud-native technologies, such as containers and microservices, empower
organizations to develop and deploy scalable, agile applications and
services in highly dynamic, distributed environments. Such systems are
designed to be resilient, elastic, and loosely coupled via manageable
abstractions and declarative APIs. This enables effective, reliable
automation that minimizes toil, and results in processes and workflows that
allow operators to make impactful changes safely and take full advantage of
these environments.
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.
If you have proposed changes, please make them via this Google Docs:
https://docs.google.com/document/d/1d9Ks3UvUV8sZj4ribAMwmq0MZwi1CwnOZWGtrCufOuk/edit
Also note that this month's edition of the Cloud Native Trail Map includes
(a slightly older iteration of) the definition:
https://github.com/cncf/landscape#trail-map
--
Dan Kohn <dan@...>
Executive Director, Cloud Native Computing Foundation https://www.cncf.io
+1-415-233-1000 https://www.dankohn.com
|
|
|
I added a comment that we’re missing the word “secure” in there.
Other than that it looks good.
Q
From: < cncf-toc@...> on behalf of alexis richardson < alexis@...>
Date: Monday, April 30, 2018 at 17:18
To: Dan Kohn < dan@...>
Cc: Alexis Richardson via cncf-toc < cncf-toc@...>
Subject: Re: [cncf-toc] Cloud Native definition last call
toggle quoted message
Show quoted text
thanks Dan
On Sun, Apr 29, 2018 at 12:52 PM, Dan Kohn < dan@...> wrote:
The TOC is aiming to create and approve a short definition of cloud native.
This is last call on making edits to the proposed text:
Cloud-native technologies, such as containers and microservices, empower
organizations to develop and deploy scalable, agile applications and
services in highly dynamic, distributed environments. Such systems are
designed to be resilient, elastic, and loosely coupled via manageable
abstractions and declarative APIs. This enables effective, reliable
automation that minimizes toil, and results in processes and workflows that
allow operators to make impactful changes safely and take full advantage of
these environments.
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.
If you have proposed changes, please make them via this Google Docs:
Also note that this month's edition of the Cloud Native Trail Map includes
(a slightly older iteration of) the definition:
--
|
|
|
We went through many iterations, but I'm pretty happy where it has landed: --- Cloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify the approach. These techniques enable loosely coupled systems that are resilient, manageable, and observable. Coupled with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil. The Cloud Native Computing Foundation seeks to drive adoption of this paradigm by fostering and sustaining an ecosystem of open source, vendor-neutral projects. We democratize state-of-the-art patterns to make these innovations accessible for everyone. --- Thanks to everyone who helped and provided feedback.
On Sun, Apr 29, 2018 at 4:52 AM Dan Kohn < dan@...> wrote: The TOC is aiming to create and approve a short definition of cloud native. This is last call on making edits to the proposed text:
Cloud-native technologies, such as containers and microservices, empower organizations to develop and deploy scalable, agile applications and services in highly dynamic, distributed environments. Such systems are designed to be resilient, elastic, and loosely coupled via manageable abstractions and declarative APIs. This enables effective, reliable automation that minimizes toil, and results in processes and workflows that allow operators to make impactful changes safely and take full advantage of these environments.
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.
|
|
|
I think it's perfect. Erin
We went through many iterations, but I'm pretty happy where it has landed: --- Cloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify the approach. These techniques enable loosely coupled systems that are resilient, manageable, and observable. Coupled with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil. The Cloud Native Computing Foundation seeks to drive adoption of this paradigm by fostering and sustaining an ecosystem of open source, vendor-neutral projects. We democratize state-of-the-art patterns to make these innovations accessible for everyone. --- Thanks to everyone who helped and provided feedback.
On Sun, Apr 29, 2018 at 4:52 AM Dan Kohn < dan@...> wrote: The TOC is aiming to create and approve a short definition of cloud native. This is last call on making edits to the proposed text:
Cloud-native technologies, such as containers and microservices, empower organizations to develop and deploy scalable, agile applications and services in highly dynamic, distributed environments. Such systems are designed to be resilient, elastic, and loosely coupled via manageable abstractions and declarative APIs. This enables effective, reliable automation that minimizes toil, and results in processes and workflows that allow operators to make impactful changes safely and take full advantage of these environments.
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.
|
|
|
Nitpick: s/the approach/this approach/
Else, it looks good. Sent by mobile; please excuse my brevity.
We went through many iterations, but I'm pretty happy where it has landed: --- Cloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify the approach. These techniques enable loosely coupled systems that are resilient, manageable, and observable. Coupled with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil. The Cloud Native Computing Foundation seeks to drive adoption of this paradigm by fostering and sustaining an ecosystem of open source, vendor-neutral projects. We democratize state-of-the-art patterns to make these innovations accessible for everyone. --- Thanks to everyone who helped and provided feedback.
On Sun, Apr 29, 2018 at 4:52 AM Dan Kohn < dan@...> wrote: The TOC is aiming to create and approve a short definition of cloud native. This is last call on making edits to the proposed text:
Cloud-native technologies, such as containers and microservices, empower organizations to develop and deploy scalable, agile applications and services in highly dynamic, distributed environments. Such systems are designed to be resilient, elastic, and loosely coupled via manageable abstractions and declarative APIs. This enables effective, reliable automation that minimizes toil, and results in processes and workflows that allow operators to make impactful changes safely and take full advantage of these environments.
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.
|
|
|
