This article explains software architecture concepts, the 4+1 view model, various architectural styles, the evolution of layered client‑server architectures, and the MVC/MVP patterns, providing a comprehensive overview of design principles and their practical implications.
The article explains why scalability is crucial for software systems, outlines the difficulty of accurately predicting future changes, and presents two architectural approaches—layer separation and abstraction/implementation layers—illustrated with diagrams and design‑pattern examples to help architects manage complexity.
This article presents a practical approach to applying layered architecture and Domain‑Driven Design (DDD) in a Java‑based fresh‑food e‑commerce platform, outlining a five‑layer microservice structure, domain partitioning guidelines, and common pitfalls to help teams build maintainable, scalable systems.
This article explains how to apply layered architecture and Domain‑Driven Design (DDD) to a Java‑based fresh‑food e‑commerce microservice system, outlining a five‑layer stack, domain partitioning, practical guidelines, and common pitfalls to help teams build maintainable, scalable back‑ends.
This article explains what software architecture is, why it is needed, the responsibilities of architects, various architecture classifications, common architectural styles such as layered, CQRS, hexagonal and onion, and introduces the COLA application architecture with its layered design, extension mechanisms and normative guidelines.
This article provides a comprehensive overview of computer networking fundamentals, covering the essence of network communication, distributed packet‑switching, layered protocol design, congestion‑control mechanisms, the evolution of network technologies, and security considerations, all aimed at helping engineers and students build a solid networking foundation.
The article explains that employing interfaces in a layered software architecture simplifies future maintenance by allowing changes to be made in a single implementation class, avoiding widespread code modifications across services, DAOs, and actions, and thereby reducing recompilation time and potential errors.
This article explores the essence of layered architecture, explaining why layering is used, its advantages and disadvantages, core design principles, and practical ways to apply logical and physical layers in real‑world software projects.
The article explains various layered architecture models—including strict, relaxed, and inheritance‑based approaches—detailing their coupling rules, implementation guidelines, code examples, and evolution through multi‑layered system designs, especially within domain‑driven design and modern front‑back separation.
This article explains seven common software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their context, problems they solve, typical solutions, drawbacks, and suitable application scenarios.
This article explains what system (software) architecture is, why it is crucial for handling software complexity, invisibility, changeability and conformity, and reviews common architectural patterns such as client‑server, peer‑to‑peer, MVC, layered, distributed‑cluster, micro‑service, event‑source, and hexagonal designs.
The Bidding Team’s DDD layered architecture consolidates all traffic in an Interfaces layer, uses a thin Application service layer to orchestrate use‑cases, places core business rules in Domain aggregates, isolates data access in Infrastructure, adds an Anti‑Corruption adapter, and employs DTOs, entities, and domain events for decoupled, consistent processing.
This article reviews Domain‑Driven Design and layered architecture fundamentals, then explains three classic DDD layered patterns—four‑layer, five‑layer, and hexagonal architectures—detailing their layers, responsibilities, advantages, drawbacks, and practical adaptations for microservice development.
The article explains seven widely used software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their contexts, problems they solve, typical structures, strengths, weaknesses, and suitable application scenarios.
This article provides a comprehensive overview of major software architecture approaches—including layered, multi‑tier, service‑oriented, and microservice architectures—explaining their motivations, structures, advantages, disadvantages, and when to apply each pattern in modern software development.
This article explains the importance of clear application layering, compares common misconceptions with Alibaba's recommended multi‑layer architecture, discusses how to implement and optimize layers such as controller, service, manager, and DAO, and outlines domain model conversions to improve maintainability and reuse.
This article explains the importance of clear application layering, reviews Alibaba's recommended layer structure, proposes an optimized layering model, and discusses domain model transformations to improve code maintainability and reuse in backend development.
The article explains seven fundamental software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their contexts, problems solved, advantages, drawbacks, and typical use cases for developers.
This article introduces seven common software architecture patterns—layered, multilayer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—explaining their context, typical problems they address, core solutions, inherent drawbacks, and suitable application scenarios for developers and system designers.
This article explains seven fundamental software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their contexts, problems they solve, typical solutions, drawbacks, and ideal use cases for developers seeking robust system designs.
This article explains seven fundamental software architecture patterns—layered, multilayer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their contexts, problems they solve, typical solutions, weaknesses, and appropriate usage scenarios for developers and designers.
This article presents a practical approach to applying layered architecture and Domain‑Driven Design (DDD) to a Java‑based fresh‑food e‑commerce microservice system, outlining five layers, their responsibilities, design principles, domain partitioning tips, and common pitfalls to help engineers build maintainable, scalable back‑ends.
Xianyu IM’s data‑sync was re‑engineered by extracting a dedicated sync layer that uses domain‑based versioning, push‑pull hybrid buffering, and priority queues, decoupling business logic, eliminating redundant pushes, and achieving a 31% latency reduction and 35% traffic savings while enabling dynamic priority adjustments.
This article explains a practical approach to applying layered architecture and Domain‑Driven Design (DDD) to a Java microservice‑based fresh‑food e‑commerce platform, outlining five architectural layers, domain service partitioning, common pitfalls, and guidance for building maintainable, high‑cohesion services.
This article explains seven common software architecture patterns—layered, multi‑layer, pipe‑filter, client‑server, MVC, event‑driven, and microservices—detailing their contexts, problems they solve, typical structures, strengths, weaknesses, and suitable application scenarios to help developers choose the right architecture for their projects.
This article explains the principles, types, and layer responsibilities of DDD layered architecture, compares it with traditional four‑layer and three‑layer designs, and shows how microservices can evolve by reorganizing aggregates and applying dependency inversion across UI, application, domain, and infrastructure layers.
This article compares five common software architecture patterns—layered, event‑driven, microkernel‑plugin, microservices, and cache—detailing their structures, advantages, drawbacks, and ideal use cases, helping architects choose the most suitable design for new or existing applications.
This article explains how business architecture controls system complexity through layered structures and domain‑driven design, compares traditional three‑tier and microservice architectures, highlights common pitfalls, and offers a lightweight domain‑centric approach for scalable, maintainable backend systems.
The article explains common misconceptions about application layering, presents Alibaba's multi‑layer architecture (open‑interface, terminal display, web, service, manager, DAO), proposes an optimized layering model with RPC, and discusses domain‑model conversions such as DO, DTO, BO, AO, VO and Query to achieve clear responsibilities and maintainable code.
The article discusses the importance of clear responsibilities in application layering, compares Alibaba's multi‑layer architecture with an optimized model, explains domain object types across layers, and offers practical guidelines to improve maintainability and reuse in backend systems.
This article explains the fundamentals of computer network architecture, the purpose and benefits of protocol layering, compares the OSI and TCP/IP models, details each TCP/IP layer and its common protocols, and walks through the TCP three‑way handshake and four‑way termination process.
This article describes AutoHome's data warehouse architecture, detailing its background, business pain points, layered model design (RDM, ADM, GDM, FDM, Stage/BDM, DIM, TMP), advantages in performance, cost, efficiency, quality, and various application scenarios including BI, analytics, and decision support.
This article introduces ten widely used software architectural patterns—including layered, client‑server, master‑slave, pipe‑filter, broker, peer‑to‑peer, event‑bus, MVC, blackboard, and interpreter—explaining their structures, typical applications, advantages, and disadvantages, and provides a comparative overview.
This article explores the essential constraints of logical architecture, discusses software design principles and patterns for reuse, examines various reuse strategies, and details how logical architecture can be layered and partitioned across different granularities to improve maintainability, scalability, and efficiency.
This article explains the fundamental concepts of software architecture, distinguishes systems, subsystems, modules, components, and frameworks, outlines various architecture layers and classifications, describes architecture levels, tracks the evolution from monolithic to micro‑services, and discusses how to evaluate and avoid common architectural pitfalls.
This article explains the classic definition of patterns, introduces architecture patterns, and reviews five common software architecture styles—layered, microservices, microkernel, event‑driven, and cloud‑native—detailing their principles, advantages, drawbacks, and typical use cases, helping developers choose the right structure for complex systems.
The article outlines the background, design principles, layered implementation details, and optimization considerations of a reusable, extensible basic framework architecture that separates business, functional, UI, and support layers to reduce coupling and accelerate app development.
This article explains how to build a data warehouse from scratch, covering its definition, system and collaboration layers, ETL requirements, data layering design, modeling steps, common challenges, and governance practices such as temporary table management and coding standards.
This article explains the layered design concept for network protocols, detailing the OSI seven‑layer model and the TCP/IP four‑layer model, their functions, and how they simplify communication, troubleshooting, and service provision across network devices.
This article explores the principles of Clean Architecture, explains layered thinking and dependency rules, discusses how to apply them in real projects, and reflects on the broader meaning of software architecture, including domain‑driven design and practical advice for developers seeking to improve their design skills.
The article explains why clear application layering—controller, service, manager, DAO—is essential for maintainable backend code, reviews Alibaba's official layer definitions, proposes an optimized layering model with a Thrift TService layer, and discusses domain model conversions to balance reuse and simplicity.
When creating software or solution architecture diagrams, it is essential to consider layered structures, platform and service distinctions, SOA principles, and the separation of application and technical views to effectively communicate enterprise‑wide or single‑system designs.
This article introduces a layered testing methodology that separates presentation, core, and foundation layers, explains test case specifications and naming conventions, provides Java code examples for atomic, basic, and framework layers, and discusses optimization techniques such as data construction, regression testing, and exception validation to improve automation efficiency.
This article introduces ten widely used software architectural patterns, explains their structure and key characteristics, and lists typical application scenarios for each, helping developers choose appropriate architectures for large‑scale enterprise systems.
This article explains the fundamentals of network communication protocols, describing the OSI seven‑layer model, its simplification to the TCP/IP four‑layer architecture, and detailing the functions of each layer—from the network interface up to the application layer—using clear analogies and packet examples.
This article explains the essence of high cohesion and low coupling, why they reduce maintenance cost, and provides practical steps—defining responsibilities, categorizing layers, and setting clear boundaries—to achieve a well‑structured, loosely coupled software system.
This article explains how software complexity arises from both business requirements and quality attributes, discusses the challenges of technical and business complexity, and demonstrates how Domain‑Driven Design—through layered and hexagonal architectures, bounded contexts, and micro‑service decomposition—helps isolate concerns and manage complexity in large systems.
The article explains why clear separation of responsibilities among controller, service, manager, and DAO layers is essential for maintainable backend code, outlines Alibaba's layered architecture guidelines, proposes an optimized layering model, and discusses domain model conversions across layers to avoid excessive object transformations.
This article examines Alibaba's Java framework layering approach, detailing each tier—from open API to DAO—while offering best practices for exception handling and domain model conventions to achieve clearer business logic and more maintainable code.
This article explains that the essence of internet layered architecture is the movement of data, detailing each layer—from client to service to database—how protocols and data formats shape the flow, and why encapsulation and reuse are key principles for evolving scalable systems.
The article outlines essential website architecture patterns—layered design, separation, distribution, clustering, caching, asynchronous processing, redundancy, automation, and security—explaining how each contributes to high concurrency, scalability, reliability, and maintainability of large web applications.
These notes distill Mark Richards' O'Reilly guide on software architecture patterns, explaining layered, event‑driven (mediator and broker), microkernel, microservices, and space‑based architectures, their key concepts, examples, trade‑offs, and evaluation criteria to help developers select the most suitable pattern for their projects.
This article discusses the challenges of building large distributed systems, emphasizing the need for a unified internal language, model‑driven design, layered architecture, and clear interface design principles to improve communication, maintainability, and scalability.
This article examines essential concepts such as modules, components, patterns, and layers, outlines common layering schemes, and details both runtime and source‑code organization considerations—including requirements compliance, performance, manageability, security, reliability, extensibility, portability, and documentation—to guide effective software architecture design.
The article explains how to analyze a purchase‑order creation requirement, identify core domain objects, design a layered Java backend using the SSH framework, and implement clean, maintainable code with proper business‑rule validation and service‑DAO separation.
This article explains what network protocols are, why layered designs simplify communication, and compares the OSI seven‑layer model with the TCP/IP reference model, detailing each layer’s functions, typical protocols, and practical examples.
