Why Cloud Native Matters: From Docker to Serverless Explained

Kubernetes

K8S (short for Kubernetes) is the common abbreviation.

Docker is powerful but becomes a “toy” for larger companies with many services, especially after the micro‑services boom.

While Docker solves single‑service delivery, real applications involve many inter‑dependent services, creating new orchestration challenges.

This led to three major orchestration projects: Docker Swarm, Apache Mesos, and Google Kubernetes, with Kubernetes becoming the dominant standard. The name reflects its role as a “helm” for containers.

Kubernetes abstracts Docker management through layers: the smallest scheduling unit is a Pod (not a container), Pods share resources, Deployments manage rollout and scaling, and Services handle load balancing and scheduling.

By abstracting these resources, Kubernetes makes container operations programmable.

Cloud Native

With Kubernetes ready for production, we can move on.

Java back‑ends often use Spring MVC (a 2002 framework) or Spring Boot, while front‑end frameworks have proliferated, leading to inconsistent best practices that hurt maintainability.

Cloud native is essentially the best practice for cloud (especially K8S) applications.

The Cloud Native Computing Foundation (CNCF) curates a landscape of projects, such as Helm, which packages K8S applications for one‑click deployment.

Serverless

Serverless is a cloud‑native use case that abstracts away operations; the term “no‑server” is misleading, “no‑ops” is more accurate.

Operations typically involve provisioning IaaS resources, testing/releasing/scaling, monitoring/logging, etc.

To hide these tasks, the industry offers BaaS (Backend as a Service) and FaaS (Function as a Service).

BaaS: abstracts common back‑end services (storage, messaging) behind SDKs/APIs.

FaaS: abstracts individual functions for specific scenarios, e.g., Google’s Knative.

Choosing a model balances flexibility and convenience: IaaS > CaaS > PaaS > FaaS > BaaS > SaaS.

Serverless gives developers a way to hide operations while retaining flexibility.

Industry Status

The article focuses on cloud‑native products built on Docker/K8S, listing major offerings:

K8S & CaaS

Google Kubernetes Engine

Google Cloud Run

Amazon EKS

Azure AKS

Alibaba Cloud Container Service

FaaS

Google Cloud Functions

AWS Lambda

ZEIT Now

Alibaba Cloud Function Compute

BaaS

LeanCloud

BaaS + FaaS

Alibaba Cloud Mini‑Program Cloud

Two personal examples illustrate the benefits:

Deploying a project with Docker + K8S simplifies installation and configuration compared to traditional on‑premise setups.

Long‑tail applications can be modernized with FaaS or BaaS, reducing operational overhead.

These cases reflect broader industry trends.

Conclusion

The article briefly covered basic cloud‑native concepts, their evolution, and current mainstream solutions, aiming to give readers a feel for the topic and encouraging hands‑on exploration.