Tencent Online Education: Cloud Migration and Cloud‑Native Architecture Evolution
Since 2017, Tencent Online Education has migrated its siloed, self‑developed services to a unified cloud‑native architecture—standardizing micro‑services, selecting open‑source middleware, and enhancing DevOps with Kubernetes, CI/CD, and data migration—thereby boosting development efficiency, scalability, cost savings, and fostering a collaborative engineering culture.
Since 2017, the Tencent Online Education department has been combining its self‑developed business cloud‑migration project with a broader cloud‑IaaS migration, open‑source middleware selection, and cloud‑native development model, driving extensive practice and reflection on backend architecture evolution.
1. Background of Self‑Developed Business Cloud Migration
The historical development model at Tencent was "siloed" – each BG or department maintained its own technology stack, leading to duplicated effort, lack of sharing, limited open‑source influence, isolated data, and no unified technical map.
Repeatedly building wheels for each BG/department.
Insufficient inter‑department collaboration.
Few impactful open‑source contributions.
Data silos and closed codebases.
No unified technology roadmap.
2. Post‑930 Technical Strategy
After the 930 adjustment, Tencent established a new Cloud Business Group and a "Technology Committee" to launch two strategic directions: "Open‑Source Collaboration" and "Business Cloud Migration".
3. Value of Cloud Migration
(1) Business Value
Focus on business, improve development efficiency.
Accelerate technology renewal, maintain technical advantage in the cloud era.
Adopt better cloud‑native components (availability, stability, documentation, APIs).
Resource reuse, elastic scaling, cost optimization.
Standardized CI/CD processes.
(2) Engineer Value
Broaden technical vision, avoid isolated development.
Skills become more valuable.
Contribute high‑quality components to the cloud, increase impact.
(3) Tencent Cloud Value
Provide cloud migration experience to customers.
Help Tencent Cloud refine its cloud components.
4. Intense Team Discussion on Cloud‑Native
4.1 Key Cloud‑Native Technologies and Milestones
From Matt Stine’s 2013 proposal of cloud‑native to the widespread adoption of Kubernetes, Service Mesh, and Serverless, the concept has gained increasing attention.
4.2 Definition and Problems Solved
Cloud‑native is defined from two aspects: leveraging cloud platform advantages and solving typical internet‑scale business problems (rapid iteration, complex logic, massive users, traffic spikes, 24/7 availability).
4.3 Cloud‑Native vs. Traditional Enterprise Applications
5. Architecture Evolution and Pain‑Point Analysis
The team identified major pain points in the legacy SOA backend and proposed three focus areas: micro‑services, middleware, and DevOps, combined with cloud migration.
5.1 Micro‑Service Optimization
Standardized development specifications aligned with cloud‑native practices.
Integrated ApiGateway for unified API authentication, authorization, lifecycle, circuit‑break, rate‑limit, and monitoring.
Promoted service reuse and business‑level middle platform.
Full containerization and migration to Tencent Cloud TKE.
Open‑source middleware selection and migration plan.
Enhanced CI/CD/CO toolchain for operational efficiency.
5.2 Middleware Selection
The team built an open‑source middleware selection map, considering business fit, CNCF Landscape, community activity, cloud support, GitHub stars/issues, and licensing.
5.3 DevOps Toolchain Enhancement
Unified BlueShield CI pipelines with templates, GitHook deployment, and rich plugins.
Integrated code quality tools (Coverity) and automated testing.
Full service containerization on Docker and migration to TKE.
Kubernetes‑based persistent storage, environment variable injection, stateless services, rapid scaling.
Unified full‑link logging and call‑chain monitoring using ELK, Prometheus, Jaeger.
6. Data Migration to Cloud
Using Tencent Cloud DTS, the team achieved multi‑type relational and NoSQL database migration with binlog‑based incremental sync, zero‑downtime migration, and support for various network environments.
7. Outcomes
The cloud migration and cloud‑native transformation resulted in higher development efficiency, reduced technical debt, better scalability, cost savings, and a more open, collaborative engineering culture.
Follow the "YunJia Community" for more articles in the Tencent Online Education cloud‑migration series.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Tencent Cloud Developer
Official Tencent Cloud community account that brings together developers, shares practical tech insights, and fosters an influential tech exchange community.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
