Understanding Cloud Native: A Historical and Technical Overview of Container Technology

In a preview article the author announced two new series, "You Call This Thing Cloud Native" and "You Call This Thing Machine Learning," with this piece serving as the first installment of the cloud native series.

Rather than presenting a conventional textbook, the author chooses a conversational format to deliver accurate, easy‑to‑understand explanations of cloud native concepts.

Many people equate cloud native solely with Docker, assuming containers are just Docker containers built on Linux namespaces and cgroups, but the reality is broader.

The author raises several questions: what is the essence of containers, why have they become so popular now, why weren’t they popular earlier, and why did virtual machines appear before containers?

To illustrate the development timeline, the author created an HTML page that visualizes key milestones in container‑related technologies.

The timeline reveals that VMware Workstation 1.0 was released in 1999, followed several years later by Linux’s namespace and cgroup mechanisms; LXC (Linux Containers) emerged in 2008, paving the way for container concepts and tools.

Although Docker popularized containers, its first open‑source release in 2013 actually used LXC under the hood, so Docker was more of a wrapper than a novel invention.

The real breakthrough was Docker’s image technology, which allowed developers to package not only the application and its startup scripts but the entire runtime environment, enabling identical deployments on local machines and in the cloud.

The surge in 2013 coincided with the shift from PC‑centric internet to mobile internet, where rapid scaling and frequent releases (often weekly or daily) created a strong demand for fast, repeatable deployment pipelines.

Earlier, web services were modest, and a single virtual machine sufficed; as application scale and traffic grew, the need for rapid, automated deployment became critical.

While containers are lighter than virtual machines, their lighter weight is a secondary benefit; the primary driver was the ability to encapsulate the full environment, which earlier virtual machines did not address.

Looking at the historical timeline shows that containers are essentially a simple combination of existing Linux mechanisms that existed long before they were needed or widely adopted.

The article concludes by noting that terms such as VM, namespace, cgroup, LXC, container, image, LibContainer, RunC, Kubernetes, OCI, CNCF, and Containerd need not be mastered immediately; the goal is to spark curiosity and provide motivation to explore Docker and related technologies further.

Additionally, the article includes a set of promotional links to other technical articles covering topics like UUID replacement, high‑availability design, message queue patterns, and interview questions.