Understanding Cloud Native: History, Ecosystem, and Core Principles

Cloud native is defined as a best‑practice path that enables software to be born, grow, and run on the cloud with minimal cognitive load, leveraging immutable infrastructure and container technology to maximize cloud value.

1. History of Cloud‑Native Technologies

2004‑2007: Google internally used container‑like cgroups at large scale.

2008: cgroups merged into the Linux kernel.

2013: Docker project released, providing OS‑level sandboxing.

2014: Kubernetes released, open‑sourcing Google’s Borg/Omega ideas.

2015: CNCF founded by Google, Red Hat, Microsoft and others; Kubernetes became its first hosted project.

2017: CNCF grew to 170 members and 14 sandbox projects.

2018: CNCF’s third anniversary saw 195 members, 19 sandbox projects and 11 incubating projects.

2. Current Cloud‑Native Ecosystem

The CNCF landscape (https://github.com/cncf/landscape) now lists over 200 projects, including Kubernetes, container runtimes, storage, networking, observability, security, and serverless solutions, all forming the foundation of modern cloud computing.

3. Definition and Scope of Cloud‑Native

Cloud native is a set of architectural guidelines that ensure applications are "born on the cloud," self‑contained, and able to exploit cloud capabilities such as scalability, portability, and automated operations.

The technical scope includes:

Application definition and development (images, CI/CD, messaging, databases).

Orchestration and management (scheduling, service discovery, API gateways, service mesh).

Observability (monitoring, logging, tracing, chaos engineering).

Underlying infrastructure (container runtimes, storage, networking).

Tooling (automation, image registries, security, secret management).

Serverless (FaaS, BaaS, pay‑as‑you‑go models).

4. Two Foundational Theories

Immutable infrastructure – achieved via container images that are unchangeable and portable.

Cloud‑application orchestration – embodied by the container design pattern introduced by Google and realized in Kubernetes.

5. Evolution Toward Immutable Infrastructure

Traditional mutable servers require manual SSH updates and configuration changes, whereas immutable container images enable seamless replacement, consistent environments, and predictable deployments across any cloud region.

Benefits include consistent, reliable infrastructure and self‑contained images that can be moved anywhere, simplifying scaling, automation, and operational control.

6. 2019 – The Year Cloud‑Native Went Mainstream

In 2019, major cloud providers and enterprises (e.g., Alibaba Cloud) announced full cloud‑native adoption, making Kubernetes a required skill and driving a surge in jobs and investments in cloud‑native architectures.

Author: Zhang Lei, Senior Technical Expert, Alibaba Cloud Container Platform, CNCF Ambassador.