Tagged articles
architecture evolution
27 articles · Page 1 of 1
This chapter summary traces the evolution from monolith to microservices, detailing core components like service discovery, circuit breakers, gateways, and observability, while stressing that adoption must be driven by business complexity and team needs — not service count — and provides a practical checklist for splitting and transformation.
API GatewayCircuit BreakerConfiguration Center
0 likes · 10 min read

This article traces the evolution of traffic recovery from manual DNS changes taking 47 minutes to fully automated 90-second failover, detailing the three-layer scheduling architecture, multi-source voting, capacity verification, batched switching, and protection mechanisms that make automatic failover safe at 10M QPS scale.
10M QPSDNSFailover
0 likes · 29 min read

Tencent's ad platform evolved from human-led refactoring with AI Copilot to Loop Engineering—a closed-loop system using data cut planes for observable verification and four specialized agents to automate refactoring of a 300k-line service, cutting cycle from months to weeks and manual diffs from 9 to near zero.
AI-assisted developmentLoop EngineeringTencent advertising platform
0 likes · 31 min read

The article explains how enterprise architecture, layered architecture, SOA, microservices and cloud‑native each address different scales of system design, shows how they can coexist in a retail modernization roadmap, and guides architects on selecting and integrating the appropriate approach for each problem domain.
Layered ArchitectureSOAarchitecture evolution
0 likes · 29 min read

This article examines the three major phases of Chinese commercial banks' core system architecture—system budding, centralized mainframe, and distributed designs—analyzes the technical improvements and shortcomings of each generation, and forecasts post‑distributed trends such as domestic‑technology adoption, cloud‑native deployment, intelligent operations, real‑time data warehousing, micro‑service structures, and large‑model integration.
Intelligent Operationsarchitecture evolutionbanking core systems
0 likes · 23 min read

This article traces the historical evolution of software architecture—from early monolithic programs likened to straw huts, through layered, distributed, and microservice designs, to modern cloud‑native and AI‑driven approaches—explaining why each shift addresses growing complexity and organizational needs.
architecture evolutioncloud-nativedistributed systems
0 likes · 9 min read

This article details the evolution of a fast‑growing finance reporting system from a monolithic microservice architecture plagued by data inconsistency, low efficiency, and scalability limits to a robust, high‑performance big‑data warehouse built with layered data models, SparkSQL processing, and unified scheduling, highlighting design decisions, technical trade‑offs, and measurable performance gains.
Spark SQLarchitecture evolutiondata warehouse
0 likes · 23 min read

At the 2024 Data Intelligence Conference, ICBC's Big Data and AI Lab detailed the evolution of its data intelligence platform, covering architectural redesign, real‑time data warehouse technology, unified intelligent data tools, and future development directions to boost efficiency and innovation.
architecture evolutionbig datadata platform
0 likes · 3 min read

The article recounts Meituan Dianping’s transaction system evolution—from a simple MVC design to microservices and a plug‑in platform—illustrating how domain‑driven design’s ubiquitous language, bounded contexts, and strategic modeling guided the separation of core, supporting, and generic domains and enabled scalable, maintainable architecture.
architecture evolutionbackend developmentdomain-driven design
0 likes · 20 min read

This article details Baidu Zhidao's migration from a legacy, high‑traffic monolithic system to a cloud‑native architecture, covering background challenges, solution selection, traffic switching, scaling practices, gateway overhaul, and the resulting stability, cost, and performance benefits.
Cloud Migrationarchitecture evolutiontraffic switching
0 likes · 14 min read

The Venus log platform at iQiyi migrated from an ElasticSearch‑Kibana architecture to an Iceberg‑based data lake with Trino, cutting storage and compute costs by over 70%, boosting stability by 85%, and efficiently supporting billions of daily logs through write‑heavy, low‑query workloads.
Elasticsearcharchitecture evolutionbig data
0 likes · 22 min read

This article explores Huolala’s evolution of application architecture—from a single monolithic system through RPC and SOA to microservices and service mesh—detailing the challenges, technical trade‑offs, and framework selections such as Dubbo, Spring Cloud, and Istio for robust backend governance.
DubboJavaarchitecture evolution
0 likes · 14 min read


DevOpsNov 10, 2022 · Cloud Native
This article reviews the 15‑year evolution of software architecture—from early monolithic systems through distributed, SOA, and microservice designs—highlighting how business drivers, cloud‑native adoption, and enduring architectural goals have shaped modern software engineering.
architecture evolutioncloud-nativedigital transformation
0 likes · 13 min read

The article examines Baidu's Contract Advertising Platform, detailing its shift from a monolithic, siloed design to a DDD‑driven microservices architecture using COLA, CQRS, and layered governance, and shares best practices for handling complex B2B advertising scenarios, service iteration, and evolving business needs.
B-end SystemsBaiduCQRS Pattern
0 likes · 27 min read

This article walks through the evolution of a high‑traffic e‑commerce site—from a single‑machine setup to cloud‑native microservices—detailing each architectural milestone, the problems it solves, key technologies involved, and design principles for building scalable, highly available systems.
CachingHigh Availabilityarchitecture evolution
0 likes · 22 min read

This article outlines Huolala's journey through five architectural stages—monolith, RPC, SOA, microservices, and service mesh—detailing the motivations, challenges, and technical choices such as Dubbo, Spring Cloud, and Istio that shaped its high‑availability, cloud‑native backend platform.
DubboJavaService Governance
0 likes · 13 min read

Vivo’s vmonitor system replaces its legacy RabbitMQ‑based pipeline with an HTTP‑driven collector and gateway, stores minute‑level JVM, system, and business metrics in a customized OpenTSDB on HBase, adds precise floating‑point handling and null‑aware aggregation, buffers data in Redis, and provides multi‑dimensional alerts comparable to Zabbix, Open‑Falcon, and Prometheus.
Distributed MonitoringJVM monitoringOpenTSDB
0 likes · 18 min read

The article explains how increasing business complexity and throughput demands drive system splitting, architectural evolution, and the adoption of scaling, sharding, caching, and asynchronous messaging techniques to improve capacity, robustness, and maintainability of large‑scale backend services.
Asynchronous ProcessingCachingHorizontal Scaling
0 likes · 7 min read

This article walks through eight progressive architecture upgrades—starting with physically separating the web server and database, adding page and fragment caches, scaling web servers, sharding databases, and finally adopting distributed caching—to illustrate how a high‑traffic site can maintain performance and reliability.
CachingWeb Scalingarchitecture evolution
0 likes · 11 min read

The article reviews Alibaba's architectural evolution from early PHP and JavaBean systems through EJB, Spring, and service‑oriented transformations using EDAS, DRDS, and ONS, highlighting challenges such as maintenance, data silos, database limits, and the resulting enterprise‑grade cloud‑native solutions.
AlibabaDatabase Migrationarchitecture evolution
0 likes · 10 min read


21CTODec 19, 2018 · Cloud Native
Over four years, MuleSoft’s website transitioned from a tightly‑coupled monolithic system to a coarse‑grained SOA with an ESB, and finally to fine‑grained microservices deployed on cloud platforms, highlighting the benefits, challenges, and practical considerations of each architectural style.
MuleSoftSOAarchitecture evolution
0 likes · 6 min read


21CTOJul 29, 2018 · Backend Development
This article explains why growing business complexity and throughput demand system decoupling, outlines horizontal scaling, vertical and business splitting, database sharding techniques, and shows how architectural evolution leads to micro‑service‑based, resilient infrastructures.
Horizontal Scalingarchitecture evolutiondatabase sharding
0 likes · 9 min read

The article reviews how increasing business complexity and throughput demands drive the need to split applications and databases, adopt horizontal and vertical scaling, implement business and service-level partitioning, and evolve system architecture toward micro‑services, caching, and asynchronous processing.
Horizontal Scalingarchitecture evolutiondatabase sharding
0 likes · 9 min read

This article describes how Tongcheng Travel’s monitoring system evolved from a monolithic design to a distributed and big‑data‑based architecture, introducing real‑time processing with Storm, machine‑learning‑enhanced alerts, and a multivariate linear regression model that dramatically improves traffic anomaly detection accuracy.
architecture evolutionbig datamachine learning
0 likes · 10 min read

The article traces Meipai’s live‑streaming barrage system from its rapid 2016 launch through successive architectural refinements that enabled it to sustain millions of concurrent users, handle extreme read‑write loads during celebrity streams, and achieve stable, high‑performance service at massive scale.
architecture evolutionbackend developmentbarrage system
0 likes · 2 min read

The article examines the rapid expansion of live streaming, detailing Meitu’s architectural upgrades for media and barrage services and Hulu’s DASH‑based system with novel features, highlighting how these advancements meet soaring user demand and illustrate the technology’s maturation into a robust, systematic field.
DASHVideo Technologyarchitecture evolution
0 likes · 5 min read


21CTOOct 26, 2015 · Artificial Intelligence
This article traces the evolution of Weibo's recommendation architecture across three major phases—independent 1.0, layered 2.0, and platform‑centric 3.0—detailing the driving business and technical factors, architectural components, advantages, shortcomings, and key outcomes of each stage.
AI EngineeringRecommendation SystemWeibo
0 likes · 19 min read
