Cloud Native 8 min read

What’s Next for Cloud Native? Insights from CNCF TOC Member Zhang Lei

In this interview, CNCF Technical Oversight Committee member Zhang Lei discusses the evolution of cloud native technologies, recent industry shifts, future directions, and practical advice for developers to stay competitive amid the rapid growth of the cloud native ecosystem.

Alibaba Cloud Developer
Alibaba Cloud Developer
Alibaba Cloud Developer
What’s Next for Cloud Native? Insights from CNCF TOC Member Zhang Lei

Q: How do you view the development and evolution of Cloud Native in recent years?

Zhang Lei : With the widespread adoption of cloud native, we see a new application delivery model combining standard application models and mesh‑based progressive releases becoming mainstream for building application platforms.

Cloud native is essentially a set of best practices that leverage cloud computing to reduce costs and increase efficiency for users. Its journey from inception to massive adoption reflects continuous self‑evolution and innovation.

From the 2014 Docker container boom to the rapid rise of Kubernetes after 2019, and today’s pervasive cloud native landscape, the ecosystem has evolved from concept to practice, spawning new architectures and influencing the entire cloud computing domain.

Q: What were the main changes you observed in the cloud native field last year, and what impact do you think they will have?

Zhang Lei : In 2020, cloud native’s rapid diffusion began transforming many domains by integrating them into the cloud’s capability pool, delivering significant cost‑saving and efficiency gains. For example, Alibaba Cloud contributed OpenYurt (edge containers), OpenKruise (workload management), and Virtual Cluster (serverless infrastructure) to the CNCF sandbox, while projects like OAM/KubeVela are incubating to innovate application delivery.

These open‑source initiatives provide crucial momentum for the ecosystem’s continued growth and help realize the goal of unlocking cloud computing benefits across industries.

Q: Where do you see Cloud Native heading in the future?

Zhang Lei : Cloud native is moving closer to its original vision of software being born and thriving in the cloud, yet the current stack often over‑emphasizes infrastructure abstraction while neglecting end‑user experience. The community is shifting toward “capability sinking, value rising,” focusing on user‑centric solutions such as Service Mesh, GitOps, OAM, and Dapr.

We anticipate cloud native’s agility and user stickiness will extend its influence into databases, AI, edge computing, and other verticals, ultimately embodying a truly ubiquitous cloud computing paradigm.

Q: How should technical professionals develop themselves to stay competitive amid the cloud native wave?

Zhang Lei : Cloud native is a continuously evolving theory and practice set. Professionals should maintain an open mindset, constantly learn, and apply these best practices—whether in operations or development. Embracing concepts like Kubernetes CRD Operators, GitOps, and IaC integrates operational expertise into code, offering ample opportunities for growth.

Additionally, focusing on the convergence of cloud native with vertical domains—such as Service Mesh, OAM, and Dapr—will help build a solid technical foundation for future challenges.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

open‑sourcetechnology trendsCNCF
Alibaba Cloud Developer
Written by

Alibaba Cloud Developer

Alibaba's official tech channel, featuring all of its technology innovations.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.