Tagged articles
system complexity
10 articles · Page 1 of 1
The article argues that seasoned developers improve system architecture by removing unnecessary components—such as redundant Redis caches or message queues—rather than continuously adding new ones, because each addition raises complexity and maintenance overhead, while simpler designs are easier to manage and evolve.
Message QueueSpringcomponent removal
0 likes · 3 min read

The article outlines practical principles and concrete measures—starting with a simple coordinator‑sub‑agent pattern, evolving only when bottlenecks appear, and controlling dimensions such as agent splitting, count, roles, communication, and orchestration—to prevent complexity overload in multi‑agent AI systems, and adds runtime safeguards and a step‑by‑step deployment roadmap.
AI agentsRuntime Protectionarchitectural design
0 likes · 7 min read

This article explains how applying CQRS and layered splitting—separating commands and queries across service, model, repository, and data layers—can dramatically lower system complexity, improve performance, and resolve common conflicts in high‑traffic backend applications.
Command Query Separationcqrsdomain-driven design
0 likes · 12 min read

The article explains how tactical programming—prioritizing rapid feature delivery by piling code—creates system complexity through change amplification, cognitive load, and unknown unknowns, and advocates strategic programming that invests in design, reduces dependencies and ambiguity, and builds sustainable software architecture.
code qualitysoftware designstrategic programming
0 likes · 8 min read

The article examines recent large‑scale service outages to illustrate how system complexity can be analyzed through four dimensions—component, structural, functional, and descriptive complexity—highlighting the need for comprehensive assessment to improve resilience and sustainable development.
Complexity AnalysisOperationsreliability
0 likes · 11 min read

This article examines the layered monolithic architecture style, describing classic four‑layer and five‑layer designs, their advantages and drawbacks, the impact on system complexity, change isolation, and the gap between business domains and technical implementation, and proposes modular monolith approaches to mitigate these challenges.
change isolationlayered designmodular monolith
0 likes · 13 min read

This article describes how Qunar's technology center defined, measured, and managed system complexity through a custom modeling framework, implemented a dashboard for continuous monitoring, and established an anti‑corruption governance process that limits complexity growth to maintain low maintenance costs across hundreds of applications and systems.
OperationsQunargovernance
0 likes · 14 min read

Software teams often grow to handle rising workload, yet adding features makes development exponentially harder because essential complexity dominates, hidden feature coupling and inevitable code decay increase system intricacy, and only refactoring, anti‑corrosion practices, and thorough documentation can mitigate the resulting business system complexity.
agile developmentcode-qualitycoupling
0 likes · 31 min read

This article details how Ctrip's car‑hailing and rental platforms tackled growing technical debt and system complexity by adopting Domain‑Driven Design, using event‑storming workshops, defining bounded contexts, and aligning team boundaries to improve maintainability, performance, and overall development efficiency.
Event Stormingmicroservicessystem complexity
0 likes · 14 min read

This article compares Nacos and Apollo configuration centers, examining their security models, environment isolation mechanisms, and architectural complexity, and concludes that Nacos offers a simpler and potentially safer solution for microservice deployments.
Configuration CenterNacosSpring Cloud
0 likes · 9 min read
