Tagged articles
service decomposition
70 articles · Page 1 of 1
This article explains why independently deployed services can still have chaotic internal architecture, and demonstrates how to separate business rules, use cases, ports, and adapters to ensure dependencies point inward, enabling testable, evolvable systems without mechanically applying layered templates.
Layered Testingbusiness rules isolationclean architecture
0 likes · 22 min read

The article shares three hard‑learned principles for dividing microservices—isolating core applications, avoiding delivery slowdown as teams grow, and defining service boundaries with concrete examples—illustrating why each rule matters and how it prevents outages.
core application isolationmicroservicesservice decomposition
0 likes · 3 min read

The article explains how bounded contexts, defined by language boundaries rather than functional ones, guide the logical separation of a payroll system into distinct domains, illustrating the process with concrete terminology lists, ambiguity detection, authority mapping, code examples, and deployment‑agnostic module structures.
Bounded Contextbackend architecturedomain-driven design
0 likes · 13 min read

The article uses a night‑market analogy to explain practical microservice design, covering domain‑based service decomposition, service discovery, communication protocols, data consistency strategies, fault‑tolerance, rate limiting, and monitoring, while warning against over‑splitting and unnecessary complexity.
Circuit BreakerDistributed Tracingeventual consistency
0 likes · 14 min read

The article uses a night‑market analogy to explain common microservice pitfalls—over‑splitting, poor service boundaries, fragile communication, data‑consistency challenges, fault‑tolerance, rate‑limiting, and monitoring—providing concrete examples, best‑practice rules, and Java code snippets to help teams avoid costly mistakes.
Circuit BreakerDistributed Tracingmicroservices
0 likes · 15 min read

This article provides a comprehensive overview of microservice architecture, outlining its core goals, design principles, and a wide range of decomposition, integration, database, event‑driven, observability, and cross‑cutting concern patterns, complete with practical examples and diagrams.
backend architecturedesign patternsmicroservices
0 likes · 22 min read

This article surveys common microservice design patterns—including decomposition, integration, event‑driven, cross‑cutting concerns, and observability—explaining their goals, trade‑offs, and practical implementation steps to help architects build scalable, resilient backend systems.
API gatewayObservabilitybackend architecture
0 likes · 20 min read

The article explains how a capacity‑driven microservice architecture uses performance metrics like QPS, TPS, and latency as the primary split criterion, detailing design principles, module responsibilities, and practical benefits that enable systems to handle traffic spikes without service collapse.
capacity‑driven architecturedomain-driven designhigh concurrency
0 likes · 10 min read

The article details Kuaishou architect Zhao Qingjie’s analysis of B‑end business challenges versus C‑end, outlines the multi‑dimensional governance covering service, business, storage and disaster‑recovery layers, and explains how systematic quality‑assurance, monitoring, error‑code design and organizational mechanisms dramatically improved system stability.
B-endHigh AvailabilityKuaishou
0 likes · 13 min read

Splitting a monolith into microservices can shift complexity to inter‑service communication, causing data consistency issues and CAP trade‑offs, so you must evaluate motivations, apply single‑responsibility and team‑aligned boundaries, and follow practical guidelines to ensure a sound architecture.
CAP theoremConway's Lawbackend architecture
0 likes · 11 min read

This article examines the principles of microservice decomposition and composition, analyzes the risks of improper service splitting such as communication overhead, dependency loops, and chaotic call chains, and offers concrete governance strategies to achieve a balanced, maintainable architecture.
Backendarchitecturecall chain
0 likes · 10 min read

The article explains why microservices have become a mainstream architectural style, outlines the problems of monolithic systems, presents core microservice characteristics, offers practical decomposition principles and patterns, compares microservices with monolith, distributed, serverless, SOA and service‑mesh architectures, and lists common technology stacks for implementation.
backend architecturecloud-nativedomain-driven design
0 likes · 26 min read

This article examines why microservice architecture emerged, the specific issues it addresses in monolithic systems, the challenges it introduces, and the essential design principles such as business‑logic, scalability, reliability, and performance‑driven service decomposition.
architectureservice decomposition
0 likes · 10 min read

This article outlines six fundamental microservice splitting principles—including single responsibility, appropriate granularity, interface segregation, product impact avoidance, scalability, and fault tolerance—to help architects design maintainable, decoupled, and resilient services.
Single Responsibilityfault toleranceinterface segregation
0 likes · 5 min read

This article explains how a complex supply‑chain platform with dozens of services and two client apps can be reorganized by introducing a gateway, an API aggregation layer, and a Backend‑for‑Frontend (BFF) pattern to reduce service coupling, simplify interface placement, and improve client‑specific adaptations.
API gatewayBFFSpring Cloud
0 likes · 11 min read

The article shares ten real‑world problems encountered in a Spring Cloud Alibaba microservice project—ranging from poor service decomposition and shared databases to chaotic configuration, unnecessary components, and deployment mistakes—offering insights to help teams prevent similar pitfalls.
Configuration ManagementSpring Cloud Alibababackend architecture
0 likes · 7 min read

The article examines the alluring promises of microservices—such as faster deployments, independent scaling, and team autonomy—while revealing the hidden complexities like deployment chaos, service discovery, data consistency, latency, and the nostalgic appeal of monolithic architectures, ultimately offering three key takeaways for architects.
backend architecturedistributed systemsmicroservices
0 likes · 10 min read

The article examines why many microservice migrations end up as distributed monoliths, highlighting the hidden costs, stability issues, and common pitfalls such as excessive synchronous calls and lack of protection mechanisms, and offers practical guidance to avoid these traps.
backend architecturedistributed monolithservice decomposition
0 likes · 7 min read

The article examines the pitfalls of turning a monolithic application into a ‘distributed monolith’ during microservice migration, highlighting how improper domain splitting, excessive synchronous remote calls, and lack of protective mechanisms can degrade stability and negate expected productivity gains.
backend architecturedistributed monolithmicroservices
0 likes · 7 min read

The article explains how to break down large or legacy monolithic systems into microservices by using business‑capability and sub‑domain decomposition approaches, discusses the benefits and challenges of such refactoring, and introduces the Strangler pattern for gradual migration.
business capabilitymonolithservice decomposition
0 likes · 6 min read

The article discusses various expert approaches to microservice decomposition, highlighting vertical and horizontal splits, business logic, stability, reliability, performance considerations, and team size implications, offering practical guidance for backend architects in design.
backend architectureservice decompositionsoftware design
0 likes · 10 min read

The article examines when and how large enterprises should adopt microservice architecture, discussing cultural, technical, and operational impacts, benefits of splitting monoliths, key governance considerations, and the importance of DevOps and skilled teams.
DevOpscloud nativeservice decomposition
0 likes · 9 min read

This article explains how Domain-Driven Design (DDD) can guide the decomposition of monolithic applications into microservices by introducing strategic and tactical design concepts, illustrating them with a membership‑center example, and providing detailed Go code structures and implementations.
DDDGoservice decomposition
0 likes · 14 min read

This article systematically explores the challenges of microservice service splitting—from technical choices and architectural reliability to business model validation and team collaboration—offering static and dynamic solutions, design principles, and practical guidelines for effective service decomposition.
backend designenterprise architectureservice decomposition
0 likes · 7 min read

This article explains the fundamentals of full‑chain gray releases in microservice architectures, covering service hierarchy, high‑cohesion low‑coupling design, deployment strategies with Kubernetes namespaces, traffic routing rules, and the essential infrastructure components needed for robust cloud‑native applications.
Gray ReleaseTraffic Routingmicroservices
0 likes · 9 min read

This article systematically explores the challenges of microservice decomposition, presenting static and dynamic solutions, architectural principles, and practical guidelines to help organizations design scalable, reliable, and business‑aligned service boundaries.
enterprise strategymicroservicesservice decomposition
0 likes · 9 min read

This article explains the challenges introduced by breaking a monolithic application into microservices, discusses CAP and BASE theories, Conway's law, and provides concrete strategies such as single‑responsibility splitting and team‑aligned architecture to help engineers design well‑structured distributed systems.
CAP theoremConway's Lawbackend architecture
0 likes · 11 min read

The article explains how many microservice migrations end up as “distributed monoliths,” detailing why splitting a monolith without proper domain design and protective mechanisms can worsen stability, increase latency, and fail to deliver the promised efficiency gains.
distributed monolithmicroservicesservice decomposition
0 likes · 7 min read

Baidu Wenku revamped its download function by breaking the monolith into an independent microservice, establishing unified protocols, a modular framework for security, rate‑limiting and logging, and real‑time monitoring, which reduced maintenance costs, improved user experience, and enabled rapid, system‑wide updates.
Baidu Wenkumicroservicesservice decomposition
0 likes · 16 min read

This article provides a comprehensive overview of microservice architecture, detailing its core objectives, design principles, various decomposition and integration patterns, database strategies, consistency mechanisms, observability techniques, and deployment practices for building resilient, scalable backend systems.
Observabilityarchitecturemicroservices
0 likes · 18 min read

The article explains how breaking a monolith into microservices can introduce data consistency challenges, discusses the CAP theorem and Conway's law, and provides practical guidelines—such as single‑responsibility division, team‑aligned service boundaries, and appropriate use of BASE and distributed transactions—to split services responsibly.
CAP theoremConway's LawSingle Responsibility
0 likes · 11 min read

This article outlines the essential preparations, strategic service granularity decisions, and practical splitting techniques—based on business logic, scalability, reliability, and performance—to guide teams in migrating monolithic systems to a robust microservice architecture.
backend architecturemigrationservice decomposition
0 likes · 10 min read

This article examines the transition from monolithic to microservice architectures, outlining the advantages and costs of microservices, the conditions under which they should be adopted, practical implementation options, risk assessments, service‑splitting strategies, and a concise comparison with SOA.
architecturerisk assessmentservice decomposition
0 likes · 17 min read

This article explains the fundamentals of microservices architecture, compares it with monolithic (integrated) systems, outlines the problems solved by microservices, details their advantages and disadvantages, provides a practical Java Spring example with code snippets, and discusses strategies for service decomposition and migration.
BackendDevOpsarchitecture
0 likes · 20 min read

This article explains the fundamentals of microservice architecture, contrasts it with monolithic designs, outlines the problems microservices solve, lists their advantages and drawbacks, provides a hands‑on code example, and describes practical strategies for splitting and migrating legacy systems.
Backendarchitecturemicroservices
0 likes · 19 min read

The article examines why growing business complexity and throughput demands necessitate system decomposition and architectural evolution, detailing horizontal scaling, vertical and business splitting, database partitioning strategies, cache and index integration, remote service data sourcing, and asynchronous messaging to achieve scalable, robust micro‑service‑based solutions.
Asynchronous MessagingHorizontal ScalingVertical Sharding
0 likes · 9 min read

This comprehensive article explains the microservices architectural style, contrasts it with monolithic (integrated) architecture, outlines the problems solved by microservices, details design principles, splitting strategies, patterns such as Strangler and Rehab, and provides a complete Java SpringBoot example with code snippets and deployment instructions.
DevOpsdistributed systemsservice decomposition
0 likes · 23 min read

This article explores the fundamental concepts of software architecture, illustrates scaling challenges with examples like Uber and Weibo, and details multi‑tier designs, caching strategies, service decomposition, monitoring, and operational practices for building and maintaining high‑performance, billion‑user backend systems.
BackendCachingmonitoring
0 likes · 20 min read

This article explains microservices architecture, contrasting it with monolithic systems, outlines the problems it solves, lists its advantages and disadvantages, provides a concrete service example with code, and discusses strategies, principles, and patterns for splitting and evolving microservices.
DevOpsbackend architectureservice decomposition
0 likes · 18 min read

This article explores the essence of system architecture, illustrating how large‑scale services like Uber and Weibo handle massive traffic, data storage, service decomposition, multi‑level caching, and monitoring, and offers practical design principles for building robust, high‑performance backend systems.
Distributed Cachingbackend architectureperformance optimization
0 likes · 22 min read

The article explains how to determine meaningful microservice boundaries and sizes by applying bounded contexts, domain‑driven design, and Conway's law, emphasizing business capability over granularity and illustrating the approach with an online meeting‑management example.
service decomposition
0 likes · 10 min read

The article examines the limitations of microservice architectures, explains how Domain‑Driven Design (DDD) complements them by providing functional decomposition guidance, and presents a practical case study showing how clear bounded contexts and aggregate roots enable scalable, maintainable system splits.
DDDdomain-driven designmicroservices
0 likes · 9 min read

The article explores practical design principles for microservice architecture, covering core concepts, team and database partitioning, API granularity, domain‑composed services, gateway strategies, shared JAR dependencies, decoupling techniques, and change‑impact analysis to guide robust backend system development.
API Designbackend architecturedatabase-splitting
0 likes · 16 min read

This article examines the trade‑offs between monolithic and microservice architectures, outlines the benefits, costs, and technical prerequisites of microservices, and provides concrete criteria—such as business complexity, team size, and talent readiness—to help engineers decide the right moment to adopt a microservice approach.
architecture evaluationdeploymentmicroservices
0 likes · 17 min read

This article compares three seasoned experts' approaches to microservice splitting—vertical vs. horizontal, business‑driven, stability‑driven, and performance‑driven—highlighting trade‑offs, team size considerations, and practical guidelines for achieving scalable, maintainable architectures.
backend architecturemicroservicesservice decomposition
0 likes · 9 min read

This article examines the transition from monolithic to microservice architecture, outlining the benefits and drawbacks of each, the conditions under which microservices should be adopted, the necessary technical and team resources, risk assessments, and practical guidance on service decomposition and migration.
architecturemicroservicesrisk assessment
0 likes · 18 min read

The article explores multiple expert perspectives on how to split monolithic applications into microservices, discussing vertical and horizontal decomposition, business logic, stability, reliability, performance, team size, and practical trade‑offs to guide architects in designing scalable, maintainable systems.
Backendarchitecturemicroservice
0 likes · 9 min read

The article examines microservice architecture as an abstract concept and presents three practical decomposition strategies—vertical/horizontal business split, business‑driven and team‑oriented considerations, and criteria based on logic, stability, reliability and performance—while also discussing cost, release frequency, and team size implications.
backend architectureservice decompositionsoftware design
0 likes · 8 min read

This article explains the fundamental differences between microservice architecture and traditional SOA, emphasizes the importance of proper service boundaries and DDD‑guided decomposition, and compares transaction‑script (anemic) and rich‑model approaches with code examples to illustrate how domain‑centric design improves microservice implementations.
backend architectureservice decomposition
0 likes · 12 min read

This article examines whether microservice architecture suits large organizations by outlining its cultural, technical, and operational impacts, the reasons to decompose monolithic systems, key considerations for architects, and practical guidance on avoiding deployment coupling while managing complexity.
backend architecturedeployment couplingmicroservices
0 likes · 9 min read

The article explores various microservice decomposition approaches—vertical vs. horizontal, business‑driven, stability‑based, reliability‑focused, and performance‑oriented—highlighting trade‑offs, team size considerations, and practical guidelines for achieving scalable, maintainable service architectures.
microservicesservice decompositionsoftware architecture
0 likes · 9 min read

This article examines microservice decomposition by presenting three expert‑derived splitting approaches—vertical/horizontal, business‑driven cost‑aware, and responsibility‑based—and discusses how factors such as team size, maintenance cost, scalability, stability, reliability and performance influence the optimal service boundaries.
backend architecturemicroservicesscalability
0 likes · 8 min read

This article examines the challenges of legacy systems and presents evolutionary migration, strangler, and sidecar patterns—along with data‑sync solutions and a real‑world case study—to guide incremental, low‑cost transformation of monolithic applications into microservices while preserving business continuity.
legacy systemmigrationservice decomposition
0 likes · 27 min read

This article explains how to determine the appropriate number of microservices for a large system and outlines four practical splitting strategies—by business logic, scalability, reliability, and performance—while emphasizing team size and service granularity to balance maintainability and efficiency.
backend architecturemicroservicesservice decomposition
0 likes · 6 min read

This article explains the fundamentals of microservices, contrasts them with monolithic architectures, outlines the pros and cons of each approach, and highlights key characteristics, benefits, and challenges of adopting a microservice‑based backend design.
backend designmicroservicesmonolithic architecture
0 likes · 9 min read

This article examines evolutionary architecture for microservices, outlines popular patterns such as CI/CD and the Strangler approach, explains layered and bounded‑context designs, and provides a detailed case study showing how a legacy monolithic system can be incrementally refactored into a flexible, cloud‑native microservice ecosystem.
CI/CDcloudevolutionary architecture
0 likes · 45 min read

The article shares Zhihu's multi‑year journey toward service‑oriented architecture, discussing the motivations, practical challenges, design trade‑offs, and lessons learned from microservice, RPC, and SSO‑based vertical splitting, as well as guidelines for defining service boundaries and layering.
RPCSSObackend architecture
0 likes · 10 min read

This article explores the evolution from Service‑Oriented Architecture to microservices, explaining why microservices succeed, how they differ from traditional monolithic designs, and the practical considerations for adopting them in large‑scale systems.
SOAautomationmicroservices
0 likes · 13 min read


21CTOMay 23, 2018 · Backend Development
This article explains why growing business complexity and throughput demands force a system to be split and refactored, describing horizontal scaling, vertical and business splitting, database sharding, and the resulting architectural evolution toward micro‑services.
Horizontal Scalingdatabase shardingmicroservices
0 likes · 9 min read

This article explores the essence of system architecture for massive web services, illustrating strategic and tactical considerations through examples like Uber and Weibo, and discusses key capabilities such as abstraction, classification, performance, service decomposition, multi‑level caching, distributed tracing, and continuous learning for scalable backend design.
backend designdistributed systemslarge-scale web
0 likes · 21 min read

This article examines how Yirendai tackled the high‑concurrency, big‑data challenges of internet finance by evolving its architecture through four major versions, introducing performance optimizations, service decomposition, database scaling, and cloud‑native strategies to support massive user growth while preserving a seamless customer experience.
Backenddatabase scalinghigh concurrency
0 likes · 14 min read

The article examines the advantages and drawbacks of microservices versus monolithic architectures, outlines key factors that influence the decision to split, and walks through a real‑world shared‑points project, detailing a four‑step process for decomposing a monolith into independent services.
GoProtobufRPC
0 likes · 10 min read

Microservice architecture, built using the Scale Cube Y‑axis approach, splits backend functionality into independent services with dedicated databases, enabling rapid development, continuous deployment, scalability, and fault isolation, while also introducing complexities such as distributed system management, testing challenges, and higher resource consumption.
continuous deploymentmicroservicesscale cube
0 likes · 11 min read

The article explains how a transaction system evolved from a monolithic application to a service‑oriented design, tackling issues such as RPC‑induced coupling, state explosion, and distributed consistency by introducing reliable event‑driven mechanisms, a core StoreEngine, and an ActorEngine framework.
actor modelevent-drivenreliability
0 likes · 8 min read


DevOpsMay 25, 2017 · Backend Development
The article narrates a Chinese state‑owned enterprise’s struggle with heterogeneous legacy systems, the introduction of an SOA strategy, and a contrasting startup’s shift to microservices, highlighting technical, operational, and cultural challenges of modernizing large‑scale software.
SOAmicroservicesservice decomposition
0 likes · 9 min read


DevOpsMar 30, 2017 · Cloud Native
The article explains microservice architecture as a set of small, independently deployable services communicating via lightweight protocols, contrasts it with monolithic applications, and discusses its benefits, challenges, organizational impact, and common integration patterns such as REST, messaging buses, and service boundaries.
RESTarchitecturemonolithic
0 likes · 11 min read

The article outlines the five‑year evolution of Qunar's payment platform from a tightly coupled monolith (1.0) to a highly available, service‑oriented distributed architecture (2.0), detailing component breakdown, challenges, and the resulting core transaction, payment, cashier, and API layers.
Financial Technologybackend architecturedistributed systems
0 likes · 9 min read

This article chronicles the five‑year evolution of Qunar's payment platform from a tightly coupled monolithic system to a high‑concurrency, highly available distributed architecture, detailing the motivations, service‑oriented splits, core components, and checkout variations that enabled support for diverse payment scenarios.
Qunarbackend architecturepayment system
0 likes · 9 min read

This article details the step‑by‑step evolution of Qunar's domestic flight ticket transaction system, covering early monolithic design, service‑oriented decomposition, database schema migration, adoption of non‑relational storage, and the implementation of an ELK‑based logging and monitoring platform to improve scalability and maintainability.
elkorder managementservice decomposition
0 likes · 22 min read

The article chronicles Yirendai’s four‑stage backend evolution—detailing the bottlenecks, architectural redesigns, logging improvements, and service‑splitting strategies that transformed a single‑server system into a scalable, multi‑service platform.
BackendLoggingarchitecture
0 likes · 7 min read
