This article defines cloud native, traces its evolution from early cloud computing to modern containers and Kubernetes, outlines its core principles, and introduces representative technologies such as containers, service meshes, and microservices, highlighting current trends and future directions.
In 2024 the author reflects on a decade of backend evolution and shares a practical, experience‑driven guide to the cloud‑native stack—including Kubernetes, multi‑cloud strategies, DevOps tooling, service mesh, observability, and message‑queue choices—tailored to teams of different sizes.
The 2020‑2021 Cloud‑Native Technology Landing Survey, conducted by CNBPA, Lingqu Cloud and the Cloud‑Native Community, collected 783 responses from finance, manufacturing, energy, pharma, telecom and government sectors, revealing that cloud‑native adoption—including containers, DevOps, micro‑services, Kubernetes, Service Mesh and cloud‑native databases—has roughly doubled in production environments and is now the primary driver of digital transformation in traditional enterprises.
This article chronicles Ctrip's cloud‑infrastructure journey—from the early OpenStack‑based IAAS platform through containerization with Mesos, the migration to large‑scale Kubernetes clusters, and the adoption of cloud‑native practices that improve resource utilization, deployment speed, and application governance.
The article explains how Kubernetes has become the default platform for cloud‑native infrastructure, why Serverless and diverse application services are emerging as key trends, and how a clear definition of cloud‑native drives large‑scale technology upgrades in Chinese public‑cloud markets.
This article explores the evolution of cloud computing into its second half, defining cloud native through CNCF's perspective, tracing its history from early Linux containers and Cgroups to Docker and Kubernetes, and detailing the core technologies—containers, service mesh, microservices, immutable infrastructure, and declarative APIs—while highlighting their practical benefits for rapid iteration, automated deployment, and efficient, scalable applications.
This article explains the concept of cloud native, tracing its evolution from early cloud computing to CNCF's 2018 definition, and explores key technologies such as containers, Kubernetes, microservices, service mesh, immutable infrastructure, and declarative APIs, while also highlighting modern cloud‑native services.
This article explains the cloud‑native concept, traces its evolution from early container experiments at Google through Docker and Kubernetes to the rapid growth of CNCF, and outlines the key technologies, immutable‑infrastructure theory, and why 2019 marked a pivotal year for cloud‑native adoption.
This article explains Kubernetes' origins, its pivotal role in the cloud‑native ecosystem, practical steps for migrating legacy applications, common operational challenges, and emerging trends such as service mesh, serverless, and data‑service integration.
This article breaks down the cloud‑native concept for operations teams, explaining its meaning, the three core pillars—containerization, microservices, and container orchestration—and how adopting them can accelerate delivery, improve resilience, cut costs, and free engineers from repetitive manual tasks.
Tencent Cloud Log Service was modernized by migrating over 95 % of its components to a cloud‑native stack of containers, Kubernetes, and declarative APIs, addressing chaotic infrastructure, stateful‑to‑stateless conversion, configuration drift, upgrade risk, elastic scaling, traffic protection and observability, which cut costs by more than 20 million CNY, reduced scaling latency by 90 %, and achieved over 99.99 % availability with petabyte‑scale burst handling.
Cloud native architecture, a modern design paradigm leveraging containers, microservices, CI/CD, and infrastructure-as-code, enables flexible, scalable, and automated applications; this article explores its definition, evolution, core technologies, maturity models, benefits, challenges, and best practices for enterprises transitioning from traditional systems.
This article introduces the origins of Kubernetes within Google’s Borg project, explains the role of the Cloud Native Computing Foundation (CNCF) and its member projects, describes the core cloud‑native characteristics of containerization, dynamic orchestration, and micro‑service architecture, and reviews the Twelve‑Factor methodology for building robust cloud‑native applications.
NetEase’s cloud‑native operations team shares how they confront new challenges of Kubernetes adoption—ranging from technical stack shifts and knowledge‑base gaps to capacity planning, automated diagnostics, monitoring, alerting, and cost‑saving strategies—offering practical insights for building efficient, stable, and scalable ops systems.
This article explains the concept of cloud native, its origins in CNCF, the evolution of containers, Docker and Kubernetes, the role of micro‑services, service mesh, immutable infrastructure and declarative APIs, and highlights the key benefits such as rapid iteration, automated deployment and independent scalability.
This article explains the origins, definitions from Pivotal and CNCF, core cloud‑native technologies such as containers, microservices, service mesh, immutable infrastructure and declarative APIs, the significance of cloud native, the current ecosystem, and a step‑by‑step implementation path for enterprises.
The article explains traditional release practices, contrasts monolithic and microservice architectures, highlights challenges of scaling microservices, and shows how Kubernetes provides automation, configuration management, fault handling, and elastic scaling to streamline cloud‑native deployments.
Cloud native, coined by Matt Stine in 2013, blends DevOps, continuous delivery, microservices, and agile infrastructure into a philosophy that redesigns applications for any public, private, or hybrid cloud, emphasizing container packaging, automated pipelines, and cultural shifts to boost scalability and delivery speed.
This article describes the end‑to‑end process of selecting, designing, building, and deploying a container‑based PaaS platform for an insurance group, covering technology choices, architecture, deployment workflow, observability, monitoring, and the business impact of moving applications to a cloud‑native environment.
The article outlines the principles and practical considerations of cloud‑native architecture, covering platform‑agnostic design, container and Kubernetes foundations, microservice decomposition, CI/CD pipelines, monitoring, tracing, logging, and fault‑tolerant high‑availability strategies for building resilient distributed systems.
