Tagged articles
system splitting
11 articles · Page 1 of 1
To improve capacity and robustness as business complexity grows, this article explains system splitting—including horizontal, vertical, business, and database sharding—and architectural evolution techniques such as caching, indexing, microservices, and service governance, illustrating practical strategies for scalable, resilient backend architectures.
Cachingdatabase shardingmicroservices
0 likes · 10 min read

The article explains how increasing business complexity and system throughput drive the need for system splitting, decoupling, and architectural evolution—covering horizontal scaling, vertical and business splitting, database sharding, caching, and the transition to micro‑services to improve capacity, stability, and performance.
architecturedatabase shardingmicroservices
0 likes · 10 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 explains why large codebases should be split into distributed services, how to perform the split, the role of Dubbo in RPC communication, and provides practical tips for interviewers and candidates tackling system‑splitting questions.
Dubbobackend architecturedistributed systems
0 likes · 11 min read

To address growing business complexity and throughput demands, this article outlines systematic approaches to decompose monolithic systems—covering horizontal and vertical scaling, application and database sharding, service governance, caching, and the evolution toward microservices—highlighting practical techniques and real-world experiences.
architecturedatabase shardingsystem splitting
0 likes · 9 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 explains how increasing business complexity and throughput require system splitting, decoupling, and architectural evolution—covering horizontal and vertical scaling, database sharding, caching, and micro‑service patterns—to improve capacity, robustness, and performance of large‑scale applications.
Horizontal Scalingdatabase shardingsystem splitting
0 likes · 10 min read

This article explains why growing business complexity and throughput demands force system decoupling and architectural upgrades, then details practical approaches to system splitting—including horizontal scaling, vertical and business partitioning—and describes the subsequent structural evolution with caching, sharding, and micro‑service patterns.
backend architecturescalabilitysystem splitting
0 likes · 9 min read


JD TechJun 8, 2018 · Backend Development
The article explains how increasing business complexity and throughput demands drive system splitting—horizontal scaling, vertical and business sharding, and database partitioning—and describes the subsequent architectural evolution toward micro‑services, caching, indexing, and asynchronous processing to improve capacity, robustness, and performance.
CachingHorizontal ScalingVertical Sharding
0 likes · 10 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


21CTONov 12, 2015 · Operations
Suning’s technical team shares how they prepared for Double‑11 by splitting monolithic services into focused modules, building a robust foundational platform with cloud, middleware, and monitoring tools, refining R&D processes, and implementing comprehensive load‑testing, optimization, and emergency response plans to ensure system stability under massive traffic.
e-commerce-architectureemergency responsehigh‑traffic
0 likes · 13 min read
