Industry Insights 30 min read

How China’s Three Major Telecom Operators Tackle Cloud‑Native Adoption: Insights & Lessons

In a November 2020 CNBPS roundtable, senior architects from China Mobile, China Unicom and China Telecom shared their cloud‑native journeys, detailing platform builds, migration standards, common challenges, practical pitfalls and a forward‑looking roadmap for telecom‑wide digital transformation.

Cloud Native Technology Community
Cloud Native Technology Community
Cloud Native Technology Community
How China’s Three Major Telecom Operators Tackle Cloud‑Native Adoption: Insights & Lessons

Roundtable Overview

On November 19, 2020, at the CNBPS 2020 Beijing closed‑door meeting, solution architects from China Mobile, China Unicom and China Telecom discussed how the three major telecom operators are applying cloud‑native technologies.

Participants

Zhao Xin (Lingqueyun) – moderator.

Zhao Chun – China Mobile Innovation Center.

Zhang Yawei – China Unicom Tianhang Cloud Platform architect.

Xiao Yanchang – China Telecom Cloud‑Network Operations.

Key Achievements and Platforms

China Mobile has built a self‑developed PaaS called “Pan‑Ji PaaS”, now operating about 59 clusters, supporting more than 30 primary systems and over 100 million users, with more than 30 000 containers.

China Unicom’s “Tianhang Cloud” evolved from 2015 container‑based micro‑service and DevOps foundations to version 4.0, offering multi‑tenant, Kubernetes, and private‑cloud portal capabilities, and now serves as a unified digital foundation for the group.

China Telecom has defined a three‑level cloud‑native migration standard (L1‑L3) and a PaaS component checklist, driving a nationwide migration of roughly 4 000 IT systems within three years, with dedicated platforms such as “Yunyan”, “Yunyi”, “Yundao” and “Yunqiao”.

Common Challenges

Lengthy project approval cycles hindering rapid front‑end application delivery.

Night‑time cut‑over windows creating tight deployment schedules.

Rollback complexities and service disruption during cut‑overs.

Standardizing micro‑service granularity and avoiding “heavy” services.

Ensuring cross‑data‑center image distribution and storage performance.

Aligning technical understanding across provinces, partners and internal teams.

Practical Pitfalls and Solutions

Examples include network isolation caused by mismatched IaaS parameters, container image distribution using a hierarchical repository with Dragonfly P2P acceleration, and the need for end‑to‑end monitoring (the “Yunyan” platform) to pinpoint failures across layers.

Future Path

Operators stress that cloud‑native adoption must be driven by clear business value, provide ready‑to‑use tooling, and lower the technical barrier for developers and operators. The roadmap includes deeper promotion of cloud‑native practices, standardized PaaS components, and collaborative open‑source ecosystem building.

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.

Cloud NativeMicroservicesKubernetesDevOpsPaaSindustry insightstelecom
Cloud Native Technology Community
Written by

Cloud Native Technology Community

The Cloud Native Technology Community, part of the CNBPA Cloud Native Technology Practice Alliance, focuses on evangelizing cutting‑edge cloud‑native technologies and practical implementations. It shares in‑depth content, case studies, and event/meetup information on containers, Kubernetes, DevOps, Service Mesh, and other cloud‑native tech, along with updates from the CNBPA alliance.

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.