An Overview of Cloud Native Computing, CNCF, and the Twelve‑Factor App

In 2014 Google open‑sourced its internal container‑orchestration system Borg; lacking a governing body, Google partnered with the Linux Foundation to create the Cloud Native Computing Foundation (CNCF) in 2015, donating the rewritten Go implementation of Borg, now known as Kubernetes, as its inaugural project.

1. Cloud Native – CNCF’s mission is to foster a collaborative open‑source ecosystem that enables users to build cloud‑native applications, encouraging projects to evolve together into a mature technology stack.

1.1 CNCF Organization – Currently 25 projects have been accepted by CNCF’s Technical Oversight Committee (TOC) after a voting process; accepted projects become CNCF member projects and are classified into sandbox, incubating, or graduated stages. The publicly released Cloud Native Landscape visualizes this ecosystem.

CNCF member projects fall into twelve categories; the article highlights the first few: Orchestration – Kubernetes provides declarative, automated deployment, scaling, and management of containerized workloads; Application Development – Helm packages applications as charts for easy installation; Monitoring – Prometheus offers a low‑overhead metrics system inspired by Google’s Borgmon; Logging & Tracing – Fluentd aggregates logs, while Jaeger provides distributed tracing; Container Registry – Harbor stores, signs, and scans Docker images.

1.3 The Twelve‑Factor App – Originating from Heroku in 2012, the twelve factors (codebase, dependencies, config, backing services, build‑release‑run, stateless processes, port binding, concurrency, disposability, dev‑prod parity, logs, admin processes) guide developers in building scalable, maintainable cloud‑native services. The article also adds three supplementary concerns: API management, authentication/authorization, and monitoring/alerting.

2. Containerization – Docker packages applications and their dependencies into portable, lightweight containers that run consistently across environments, offering isolation, easy image distribution, rapid scaling, and disposable testing environments.

3. Service Orchestration – Kubernetes, Mesos, and Docker Swarm provide powerful scheduling and orchestration; Kubernetes, derived from Google’s Borg, has become the dominant platform for large‑scale container production, while Mesos excels at multi‑task workloads and custom frameworks.

4. Microservice Architecture – The article contrasts monolithic (single WAR deployed on JEE servers) with service‑oriented and microservice architectures, emphasizing independent services, REST APIs, and the role of containers in isolating each microservice. Spring Cloud’s ecosystem (service discovery, circuit breaking, routing, configuration, etc.) is illustrated alongside Kubernetes, showing complementary strengths.

5. Summary – Cloud‑native technology evolves rapidly; this article summarizes its three defining traits—containerized packaging, dynamic management, and microservice orientation—while highlighting CNCF’s role in unifying the ecosystem and the continued relevance of the Twelve‑Factor principles for building reliable cloud‑native applications.