Evolution of ZBJ.com’s System Architecture and DevOps Platform

Before 2015, 80% of ZBJ.com’s projects were developed in PHP, with a few using Node.js and Java. In 2015 the company launched the "Tengyun 7" initiative, refactoring core business code into Java and establishing a Dubbo‑centric SOA framework backed by ZooKeeper and Swoole.

The architecture later supported both new Java services and legacy PHP services, enabling cross‑language Dubbo calls. From 2016 onward, a front‑back separation strategy introduced three primary languages: Node.js for front‑end, Java for back‑end and PHP migration, and PHP for legacy maintenance.

Rapid project growth pressured development processes, leading to the adoption of agile methods and the introduction of a "deploy‑>story‑>task" hierarchy to manage releases, CMDB, and multi‑data‑center deployments.

In late 2016 a dedicated DevOps team was formed, integrating version control (GitLab), build automation (12 language‑specific compile methods), Jenkins with a master/slave architecture, and unified component repositories (Nexus, PPKG, NPM). The release pipeline evolved through three stages: a simple "big‑pot" era, a "bus" model with scheduled releases, and finally a "taxi" model featuring per‑project owners, Docker containerization, and branch strategies (branches → master → tags).

The platform provides automated testing (unit, API, performance), CMDB for hybrid cloud resource management, DNS automation, elastic scaling of VMs and containers, and comprehensive monitoring (availability, service rankings, canary analysis). Daily build counts average 1,500, with about 100 production releases per day.

Overall, the article presents a detailed case study of ZBJ.com’s DevOps evolution, highlighting challenges, solutions, and future directions such as self‑service job platforms, enhanced canary metrics, and expanded hybrid‑cloud management.