Tagged articles
layered design
52 articles · Page 1 of 1
The article provides a detailed, source‑code‑backed walkthrough of Harness’s three‑level memory system—user context, historical layering, and a structured fact list—explaining each layer’s purpose, update frequency, lifecycle, and how the surrounding middleware, queue, updater, storage, and injection modules cooperate to deliver real‑time, persistent, and searchable memory for AI agents.
AI agentDeerFlowHarness
0 likes · 27 min read

When business requirements change every few days, traditional data architectures become rigid, tightly coupled, and slow, causing endless cycles of overtime; this article analyzes the root causes and presents a layered, configurable, and API‑driven approach—including moderate redundancy, data catalogs, and decoupled layers—to enable data systems to adapt quickly and reliably.
APIconfigurable processingdata architecture
0 likes · 9 min read

Most test automation scripts start strong but quickly collapse, leading to flaky failures, duplicated locators, and maintenance overhead; this guide explains the stark difference between ordinary QA scripts and top‑1% QA engineers by presenting five core principles—layered architecture, treating the framework as software, deterministic tests, data‑driven design, and evolutionary adaptability—plus concrete code examples.
Data‑Driven TestingQA best practicesTest Automation
0 likes · 6 min read

This article explains how to design decoupled embedded software by using a layered architecture, event‑driven mechanisms, pipeline‑filter data flows, and dependency injection, providing concrete C code examples and practical guidelines for each technique to improve maintainability and scalability.
Embeddedc-programmingdependency-injection
0 likes · 16 min read

This guide explains how to achieve clean decoupling in embedded software by employing a systematic layered architecture, leveraging event‑driven and pipeline‑filter patterns for data flow, and applying dependency injection, complete with practical C code examples and best‑practice recommendations for resource‑constrained devices.
c-programmingdependency-injectiondesign patterns
0 likes · 17 min read


DevOpsSep 19, 2024 · Fundamentals
This article explains the fundamentals of software architecture, covering its definition, key components such as systems, modules, components, and subsystems, and explores vertical (layered) and horizontal (modular) architectures, design principles, complexity evaluation, cross‑platform considerations, and practical guidelines for building maintainable applications.
App DevelopmentDesign Principlescomplexity management
0 likes · 10 min read

This article explains essential software architecture concepts such as entropy and broken‑window effects, the sources and symptoms of complexity, the importance of orthogonality and consistency, and classic design principles like SOLID, DRY, and layered abstraction to guide architects in building maintainable, flexible systems.
ComplexityDRYDesign Principles
0 likes · 18 min read

This article explains the concept of layered architecture in software systems, covering common patterns like MVC and three‑tier designs, illustrating examples from networking and operating systems, and discussing the advantages, design considerations, potential drawbacks, and practical guidelines for implementing effective layer separation.
BackendDesign Principleslayered design
0 likes · 9 min read

This article explains why software architecture matters, defines the essence of Clean Architecture, compares it with Hexagonal and DDD layered models, and walks through a practical, step‑by‑step process—from business analysis and domain modeling to layer implementation and code examples—showing how to reduce complexity and maintenance cost.
BackendDDDclean architecture
0 likes · 21 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 analyzes the growing need for a unified Unity framework at AutoHome, evaluates existing open‑source Unity architectures, proposes a four‑layer design (logic, middle, base, data), demonstrates a native‑message example, and quantifies quality, efficiency, performance, and reuse gains.
Open Source FrameworksUnityarchitecture
0 likes · 12 min read

The article explains how applying clean separation, layered architecture, and the hexagonal ports‑and‑adapters pattern helps manage complexity, keep core domain logic isolated, and make software easier to change, test, and maintain.
Clean Codehexagonal-architecturelayered design
0 likes · 8 min read

This article explains how Onion Architecture, built on Domain‑Driven Design principles, organizes software into concentric layers that isolate core business logic, improve maintainability, testability, and flexibility, and outlines its layers, dependencies, services, testing strategies, and applicability to microservices.
Onion Architecturelayered designsoftware architecture
0 likes · 11 min read

This article explains how to design a well‑structured Java web application by defining clear three‑layer architecture (Controller, Service, DAO), outlining each layer's responsibilities, describing data type conventions such as PO, BO, VO, DTO, Model, and showing how these types map to the layers for maintainable, scalable development.
DAOData Transfer ObjectsJava
0 likes · 13 min read

The article discusses the importance of proper application layering in backend development, critiques common misuse of controller and service layers, outlines Alibaba's recommended multi‑layer architecture—including open API, presentation, web, service, manager, and DAO layers—offers optimization suggestions, and highlights domain model conversions.
Alibaba guidelinesDAOService Layer
0 likes · 9 min read

This article explains architectural thinking as a synthesis of system, structured, and programming mindsets, emphasizing the core principles of decomposition and integration, and describes various layered models such as cloud three‑layer, SOA, and classic three‑tier architectures for both technical and application design.
SOAarchitecturecloud computing
0 likes · 15 min read

This article presents a lightweight, domain‑model‑based layered architecture for Java backend development, detailing six layers (web, biz, dal, client, common, facade), their package structures, call relationships, layer conventions, and providing reusable code snippets and utilities to guide clean and maintainable application design.
Domain ModelJavabackend architecture
0 likes · 12 min read

This article explores layered thinking in architecture design, detailing decomposition and integration, cloud three‑layer models, SOA component‑service‑process layering, and how to combine these approaches into coherent technical and application architectures for balanced business‑technology solutions.
SOATechnical Architecturearchitecture
0 likes · 15 min read

This article explains the concept of layered thinking in architecture design, covering decomposition and integration, cloud three‑layer models, SOA component‑service‑process layering, application‑level layering, and how to combine these approaches into coherent, multi‑view architecture diagrams for both technical and functional perspectives.
SOAarchitecturecloud computing
0 likes · 16 min read

This article explores layered thinking in system architecture, covering decomposition and integration, cloud three‑tier models, SOA component‑service‑process layers, their fusion, classic and domain‑driven application layers, and practical guidance for constructing clear, multi‑view architecture diagrams.
SOAarchitecturecloud computing
0 likes · 17 min read

The article explains layered architecture thinking, covering cloud three‑tier models, SOA layering, classic three‑layer application design, domain‑driven refinements, and practical guidance on constructing clear, maintainable system diagrams without mixing incompatible modeling approaches.
SOAarchitecturecloud computing
0 likes · 19 min read

This article explains how layered thinking and layered models—covering decomposition, integration, cloud three‑layer architecture, SOA layering, and application architecture—provide a systematic approach to designing balanced, cohesive, and loosely‑coupled software systems.
SOAarchitecturecloud computing
0 likes · 14 min read

This article explains the concept of layered architecture, covering decomposition and integration, cloud three‑layer models, SOA layering, database and service layers, application and domain layers, and provides guidance on constructing clear, multi‑view architecture diagrams for complex systems.
SOAarchitecturecloud computing
0 likes · 14 min read

This article explains the classic three‑tier software architecture, detailing the responsibilities of the presentation, service, business, and data‑access layers, comparing MVC, MVP, and Presentation Model patterns, and discussing design considerations such as DTOs, WCF services, and common infrastructure for scalable enterprise systems.
Business LayerMVCService Layer
0 likes · 10 min read

This article examines the importance of clear application layering—controller, service, manager, and DAO—highlighting common pitfalls, Alibaba’s recommended architecture, and practical strategies for defining responsibilities, reducing code duplication, and improving maintainability across backend projects.
BackendDAOService
0 likes · 9 min read

This article provides a comprehensive guide to data model architecture, detailing layered data storage concepts, classification structures, naming conventions, and design principles to help practitioners build consistent, maintainable, and performant data warehouses and analytics platforms.
data modelinglayered designnaming conventions
0 likes · 9 min read

This article explores the concept of layered thinking in architecture design, covering decomposition and integration, cloud three‑tier models, SOA layering, application and technical architecture patterns, and how to combine these approaches for clear, maintainable system diagrams.
SOAarchitecturecloud computing
0 likes · 16 min read

This article explains Yanxuan's inventory center design, detailing a layered approach that separates warehouse, physical, and sales inventories, introduces lockable stock pools for complex sales scenarios, and shows how these practices improve stock turnover and reduce out‑of‑stock rates in e‑commerce.
e-commerceinventory managementlayered design
0 likes · 16 min read

This article examines Yanxuan's inventory management challenges and presents a layered design—warehouse, physical, and sales layers—combined with a flexible lock‑stock pool to support multi‑channel, multi‑warehouse operations while addressing promotional and special‑use inventory requirements.
Operationse-commerceinventory management
0 likes · 14 min read

This article explains how layered thinking and layered models guide architecture design, covering decomposition and integration, cloud three‑tier (IaaS‑PaaS‑SaaS) and SOA layering, the role of service and data layers, and how to combine cloud and SOA concepts into coherent architectural diagrams.
SOATechnical Architecturearchitecture
0 likes · 15 min read

This article explains the concept of layered architecture thinking, covering decomposition and integration, cloud three‑tier models, SOA layering, application‑level three‑tier patterns, and how to combine cloud and SOA approaches into a coherent, multi‑view architectural blueprint.
SOATechnical Architecturelayered design
0 likes · 14 min read


58UXDMar 4, 2021 · Game Development
This article explains how breaking down game UI into experience, mechanism, and presentation layers—and analyzing them vertically and horizontally—helps designers align product goals with player needs, leading to clearer layouts and stronger player engagement.
UI layoutdesign methodologygame UI
0 likes · 7 min read

This article explains why clear application layering matters, outlines Alibaba's recommended layers, proposes an optimized layering approach, details domain model mappings for each layer, and offers practical tips to improve maintainability and team collaboration in backend development.
Alibaba guidelinesDomain Modellayered design
0 likes · 9 min read

This article explains how layered thinking guides architecture design, covering cloud three‑tier (IaaS‑PaaS‑SaaS) and SOA three‑tier models, the role of decomposition and integration, and practical layering patterns for technical, application, and functional architectures across various domains.
SOATechnical Architecturearchitecture
0 likes · 21 min read

This article explains the purpose and benefits of layered software architecture, compares traditional three‑tier designs with hexagonal architecture, discusses system splitting and micro‑service considerations, and provides C# code examples illustrating domain, application, and adapter layers.
C++domain-driven designhexagonal-architecture
0 likes · 11 min read

This article explains the concept of software architecture, why it is needed, the responsibilities of architects, various architectural classifications and patterns such as layered, CQRS, hexagonal and onion architectures, and introduces the COLA framework with its layered design, extension mechanisms, and specification guidelines.
COLAOnion Architecturecqrs
0 likes · 12 min read

This article explains what software architecture is, why it is essential, the responsibilities of architects, various classification types, typical architectural patterns such as layered, CQRS, hexagonal and onion architectures, and introduces Alibaba's open‑source COLA framework with its layered design, extension and specification concepts.
COLA frameworkOnion Architecturecqrs
0 likes · 14 min read


JavaEdgeSep 25, 2020 · Backend Development
The article explains what architectural layering is, outlines its benefits such as simplified design, high reuse, and easier horizontal scaling, describes how to define layer boundaries and typical responsibilities, discusses common drawbacks like added complexity and performance overhead, and concludes with best‑practice recommendations.
architecturelayered design
0 likes · 10 min read

This article describes the background, design principles, layered architecture, and implementation details of a modular mobile framework that separates business, functional, UI, and support layers to enable rapid app development, easy extension, and reduced coupling.
Androiddesign patternslayered design
0 likes · 9 min read


21CTOJul 5, 2019 · Fundamentals
This article explains the essential considerations for creating overall and application‑level architecture diagrams, covering layered structures, SOA‑based service layers, distinctions between business and technical views, and practical tips for visualizing enterprise, IoT, and single‑system architectures.
IT infrastructureSOAarchitecture
0 likes · 8 min read


21CTOMay 20, 2019 · Fundamentals
This article explains how abstract, layered, divide‑and‑conquer, and evolutionary thinking form the four essential mental tools that enable software architects to manage complexity, design scalable systems, and continuously evolve architectures in response to changing requirements.
Divide and Conquerabstractionarchitectural mindset
0 likes · 17 min read

This article outlines the progressive evolution of a company's software layering strategy—from an initial monolithic approach through webapp, business, base, and core layers—explaining the motivations, definitions, and practical implementations of each stage.
core serviceslayered designsoftware architecture
0 likes · 6 min read

The article explains how abstraction, layered design, divide‑and‑conquer, and evolutionary thinking form the four essential mental tools for architects to manage complexity, illustrating each concept with real‑world examples, diagrams, and practical advice for cultivating these skills.
Divide and Conquerabstractionarchitectural thinking
0 likes · 14 min read

This tutorial explains how to create circular user avatars in PHP by stacking three image layers—a base layer, the uploaded user photo, and a transparent circular mask—detailing the design concept and showing the essential avatar.class.php implementation.
BackendPHPavatar
0 likes · 2 min read

This article explains why clear application layering matters, outlines Alibaba's recommended layer structure, proposes an optimized layering model with distinct responsibilities, and details domain model conventions to improve code reuse, maintainability, and team collaboration in backend development.
ControllerDAOService Layer
0 likes · 8 min read


21CTOJul 16, 2018 · Fundamentals
The article explains how mastering abstraction, layering, divide‑and‑conquer, and evolutionary thinking equips software architects to manage complexity, design modular systems, and continuously evolve architectures—from simple modules to large‑scale platforms—highlighting practical examples, interview questions, and learning pathways.
Divide and Conquerabstractionevolutionary design
0 likes · 14 min read

This article explains how abstraction, layered thinking, divide‑and‑conquer, and evolutionary design serve as the four fundamental mental tools that architects use to manage complexity in software systems, illustrated with everyday analogies, diagrams, and practical interview examples.
Divide and Conquerabstractionevolutionary design
0 likes · 15 min read

This article outlines a three‑layer, adaptable backend architecture—gateway, business, and foundation layers—detailing how to handle HTTP/TCP requests, design service interfaces, manage data models, and choose technical components to support rapidly evolving business needs.
business servicegateway layerlayered design
0 likes · 14 min read

This article explains the layered server‑side architecture model, the role of each layer, the MVC pattern and its communication flows, Maven‑based project modularization, and an overview of Service‑Oriented Architecture, providing a practical guide for designing flexible backend systems.
BackendMVCMaven
0 likes · 7 min read

This article explains how to choose an Android framework, build a layered MVP architecture, and use RxJava to move network requests off the main thread, providing clear code examples and practical tips for scalable, testable mobile apps.
AndroidMVPRxJava
0 likes · 14 min read


21CTONov 16, 2015 · Mobile Development
This article examines common architectural patterns for native mobile applications—including classic MVC, its MVVM extension, hierarchical HMVC, and various layered designs such as three‑, four‑, and five‑tier architectures—explaining their structures, advantages, and appropriate use cases to help developers choose the most efficient model.
HMVCMVCMVVM
0 likes · 7 min read

This article presents a practical IoT layered architecture model, contrasting the classic three‑tier view with a four‑tier structure (hardware, coordination, service, and application layers), explains the role of each layer, and advocates using hexagonal architecture for the service layer in the Lan platform.
IoTService Layerarchitecture
0 likes · 4 min read
