Tagged articles
service splitting
31 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 analyzes two extremes of microservice splitting—overly coarse services that become monoliths and overly fine services that explode call chains—details a three-tier technical debt classification (P0/P1/P2), and presents a four-step Strangler Fig Pattern for zero-downtime progressive refactoring based on real e-commerce production experience.
architecture governancedomain-driven designe-commerce case study
0 likes · 13 min read

This guide explains how to build a million‑request‑per‑second microservice system by properly splitting business domains, partitioning data with vertical and horizontal sharding, applying robust rate‑limiting techniques, and implementing circuit‑breaking and degradation strategies to maintain stability.
Shardingcircuit breakinghigh concurrency
0 likes · 6 min read

The article explains how adaptive modular monolith architecture lets teams develop quickly with a single deployable unit and later split modules into independent microservices by merely changing a configuration, eliminating repackaging, complex pipelines, and code modifications while preserving performance and simplicity.
microservicesmodular monolithservice splitting
0 likes · 7 min read

This article explains why overly fine‑grained service splitting hurts performance and debugging, shows best‑practice granularity aligned with team size, introduces evolutionary splitting based on model responsibilities, and walks through real‑world case studies, domain‑driven design concepts, architectural patterns such as hexagonal, CQRS, and event‑driven designs, and practical steps for building a robust service‑oriented system.
cqrsdomain-driven designevent-driven
0 likes · 6 min read

This article discusses why and how to split monolithic applications into microservices, outlining common pitfalls of over‑splitting and presenting practical principles such as team and domain isolation, the three‑person rule, read/write separation, dependency management, and service count guidelines.
backend architecturedomain-driven designmicroservices
0 likes · 15 min read

This article explains why microservices have become a dominant architectural style, outlines the problems they solve, describes core characteristics, presents various splitting principles and methods, discusses the relationship with domain‑driven design, compares microservices to other architectures, and lists common technologies and best‑practice recommendations.
DDDbackend architectureservice splitting
0 likes · 24 min read

The article explains why microservices have become a mainstream architectural choice, outlines the shortcomings of monolithic systems, presents core design principles and various service‑splitting methods, discusses the synergy with Domain‑Driven Design, compares microservices with other architectures, and lists typical technologies used in practice.
DDDbackend architecturecloud-native
0 likes · 23 min read

This article provides a comprehensive analysis of microservices, covering why they are adopted, the drawbacks of monolithic architectures, core characteristics, splitting principles and strategies, the relationship with Domain‑Driven Design, comparisons with other architectural styles, and a detailed overview of the common technical stack used to build and operate microservice systems.
DDDbackend architecturecloud-native
0 likes · 22 min read

This article examines the challenges of service proliferation in a microservice‑based system, defines modularity and granularity, and presents systematic splitting and merging factors—such as responsibility, fault tolerance, performance, scalability, cost‑benefit, and team size—using a concrete Promise service case study to guide optimal service design.
backend architectureservice granularityservice splitting
0 likes · 17 min read

This article explains microservice service‑splitting principles, demonstrates a demo project with separate order and user services, and shows how to implement remote calls between them using Spring Boot's RestTemplate, including code examples and provider‑consumer concepts.
JavaRemote CallRestTemplate
0 likes · 9 min read

This article explains microservice service‑splitting guidelines, demonstrates a small demo project with separate order‑service and user‑service modules, shows how to define independent databases, and provides step‑by‑step code for registering a RestTemplate bean and performing remote calls between services using Spring Boot.
Remote CallRestTemplateservice splitting
0 likes · 10 min read

This article explains microservice service‑splitting principles, demonstrates a small demo with separate order‑service and user‑service modules, shows how to define independent databases, and provides step‑by‑step code for registering a RestTemplate bean and performing remote calls between services using Spring Boot.
Remote CallRestTemplateservice splitting
0 likes · 9 min read

The article explains the AKF principle for microservice design, detailing how X‑axis horizontal replication, Y‑axis functional splitting, and Z‑axis data‑centric partitioning address single‑point failures, capacity limits, and performance bottlenecks by employing master‑master, master‑slave, and master‑backup replication patterns.
AKFBackendarchitecture
0 likes · 6 min read

The article explains how to address single‑node limitations by clustering servers using the AKF microservice splitting principle, detailing X‑axis horizontal replication, Y‑axis business‑oriented partitioning, and Z‑axis data‑source segmentation to achieve scalable, fault‑tolerant backend architectures.
AKF principlebackend architectureclustering
0 likes · 5 min read

This article recounts how a two‑person SaaS team evolved its architecture from a monolithic Java application to a suite of over ten Spring Cloud microservices, detailing RESTful API design, CI/CD pipelines with Jenkins, Docker containerization, Kubernetes integration, link tracing, and operational monitoring.
CI/CDDockerKubernetes
0 likes · 17 min read


21CTODec 25, 2021 · Cloud Native
This article explains why and when to break a monolithic application into microservices, outlines the business and technical signals that trigger splitting, presents guiding principles, functional and non‑functional strategies, and risk‑mitigation practices to ensure a smooth, sustainable migration.
domain-driven designmicroservicesoperational risk
0 likes · 21 min read

This article explains why, when, and how to split a monolithic application into microservices, covering the goals of splitting, timing decisions, guiding principles, granularity considerations, functional and non‑functional strategies, merging practices, and associated risks.
DDDarchitecturecloud-native
0 likes · 18 min read

The article explains the AKF microservice splitting principle, describing how X‑axis horizontal replication, Y‑axis business‑oriented partitioning, and Z‑axis data‑oriented partitioning together address single‑point failures, capacity limits, and performance bottlenecks in clustered backend systems.
AKFBackendarchitecture
0 likes · 5 min read


21CTOSep 18, 2021 · Cloud Native
This article explains why and when to break a monolithic application into micro‑services, outlines practical splitting strategies, essential design principles, and the risks involved, while providing concrete guidelines for teams, business scale, and technical readiness.
Best PracticesDDDarchitecture
0 likes · 20 min read

This article explains how Domain‑Driven Design provides a systematic approach to modeling complex business domains, guiding microservice decomposition, service boundaries, bounded contexts, and layered architectures, while addressing software complexity through strategic and tactical patterns such as SOLID, aggregates, and hexagonal design.
DDDbackend architecturedomain-driven design
0 likes · 19 min read


DevOpsJul 21, 2021 · Backend Development
This article explains why and when to split existing microservices, validates the split idea with event storming and data‑model analysis, outlines guiding principles, and provides a detailed, step‑by‑step process—including code restructuring, testing, dependency removal, and database separation—to ensure a smooth transition.
BFFarchitecturefeature-toggle
0 likes · 16 min read

This article explores the evolution of business architecture from functional to domain‑based microservice splitting, outlines service grading, identifies code coupling and unreasonable dependencies, and presents practical governance techniques such as on‑demand loading, event‑driven design, and anti‑corruption layers to improve stability and maintainability.
Service Governancebackend architectureboundary management
0 likes · 16 min read

The article outlines how a call platform’s architecture progressed through successive stages—starting with a monolithic design, then business service splitting, service governance and isolated deployment, horizontal scaling, distributed database sharding, and finally micro‑service adoption—highlighting the problems each evolution solved and the new challenges introduced.
Distributed Databasebackend developmentmicroservices
0 likes · 13 min read

The article explains how Domain‑Driven Design (DDD) complements microservice architecture by addressing functional partitioning, clarifying bounded contexts, and guiding service decomposition, while also highlighting microservices' shortcomings in handling requirement changes and offering practical guidelines for effective system splitting.
DDDdomain modelingservice splitting
0 likes · 10 min read

This article explores the concept of a “micro‑backend” by adapting micro‑frontend principles to server‑side applications, detailing how to use IoC, monorepo management with Lerna, and Midway’s configurable scanning to split a large Node.js codebase into independent, maintainable domain modules without changing developer workflows.
IoCmicro-backendmonorepo
0 likes · 10 min read

This article chronicles the evolution of MaFengWo's instant‑messaging platform, detailing the transition from a simple PHP implementation to OpenResty optimizations, the introduction of multi‑mode routing in IM 2.0, and a complete service‑oriented redesign in Go for IM 3.0, while addressing scalability, multi‑device synchronization, and message reliability.
GoIMOpenResty
0 likes · 14 min read


21CTOMay 9, 2017 · Backend Development
This article explains how Ele.me grew from a student startup to handling over nine million daily orders by evolving its website architecture, adopting SOA, splitting services, implementing a robust release system, and building comprehensive monitoring and data‑access layers.
Ele.mebackend-developmentdeployment
0 likes · 13 min read

This article explains how Taobao achieves horizontal scalability by adopting stateless session handling, efficient client‑side cookie storage, multi‑level caching, service splitting with HSF, database sharding via TDDL, asynchronous messaging, unstructured data storage, and comprehensive monitoring and configuration management.
CachingStatelessmonitoring
0 likes · 18 min read

The article explains how to build a highly scalable internet application by adopting stateless session handling, effective caching, service decomposition with remote call frameworks, database sharding, asynchronous messaging, unstructured data storage, comprehensive monitoring, and unified configuration management.
Cachingasynchronous communicationdatabase sharding
0 likes · 16 min read


21CTOApr 16, 2016 · Backend Development
Taobao’s massive B2C platform achieves high scalability and reliability by employing stateless session management with multi‑value cookies, leveraging Tair caching, splitting services via HSF, partitioning databases with TDDL, adopting asynchronous messaging, using distributed file storage, and implementing comprehensive monitoring and unified configuration management.
Cachingdatabase shardingservice splitting
0 likes · 18 min read
