Tagged articles
Onion Architecture
41 articles · Page 1 of 1
The article explains the Development View— the "code floor plan" in the 4+1 view model—by detailing how code is organized, directory structures, module dependencies, build and packaging configurations, common architectural patterns, design principles, and practical solutions to typical problems such as circular dependencies and package chaos.
Design PrinciplesOnion Architecturecode organization
0 likes · 9 min read

The article examines how software architecture has progressed from the traditional DDD four‑layer structure through Hexagonal, Onion, and Clean architectures, explaining essential versus accidental complexity, layering principles, dependency inversion, and how each pattern refines modularity, testability, and dependency direction.
DDDOnion Architectureclean architecture
0 likes · 12 min read

The article explains that Onion Architecture’s essence lies in inward‑facing dependencies rather than the visual onion shape, details its six‑layer structure, clarifies common misconceptions, and compares it with Clean and Hexagonal architectures to show how it improves testability and replaceability.
Onion Architectureclean architecturedependency inversion
0 likes · 12 min read

Hexagonal Architecture’s true essence lies in its ports‑and‑adapters structure and technology‑agnostic core, not the six‑sided diagram, and the article explains this concept, its driving vs. driven sides, its relation to DIP, common misconceptions, and how it aligns with Clean and Onion architectures.
Dependency Inversion PrincipleOnion Architectureclean architecture
0 likes · 11 min read

The article explains that Clean Architecture’s true essence lies in the immutable Dependency Rule—dependencies must always point inward—while the four‑layer diagram is merely a flexible skeleton, and it clarifies common misconceptions, ties to SOLID, and shows how to apply the rule across Hexagonal and Onion variants.
Dependency RuleOnion ArchitectureSOLID
0 likes · 12 min read

This article explains how to apply Domain-Driven Design (DDD) to a new project, covering terminology, architecture evolution from IAAS/PAAS/SAAS, bounded‑context boundaries, the four DDD layers, clean layered, hexagonal and onion architectures, and practical guidance for backend development.
Bounded ContextDDDOnion Architecture
0 likes · 9 min read

This article walks through the historical evolution of backend architecture—from early N‑layered designs, through DDD, Hexagonal, Onion, and finally Clean Architecture—explaining why each style emerged, how they differ, and what practical rules developers can follow to manage complexity and dependencies.
DDDN‑layeredOnion Architecture
0 likes · 17 min read

This article explains how to apply Domain‑Driven Design (DDD) to a new project, covering key terminology, architectural evolution, bounded contexts, the four DDD boundaries, and various layered architectures such as clean, hexagonal, and onion models.
DDDOnion Architecturehexagonal-architecture
0 likes · 9 min read

This article explains how to start a new project using Domain‑Driven Design, covering terminology, architectural evolution across SaaS, PaaS, IaaS, bounded‑context division, the four DDD boundaries, clean layered, hexagonal and onion architectures, and concludes with practical guidance.
Bounded ContextDDDOnion Architecture
0 likes · 8 min read

This article explains how to apply Domain‑Driven Design (DDD) to a brand‑new project, covering essential terminology, architecture evolution across SaaS, PaaS, IaaS, bounded‑context segmentation, the four DDD boundaries, clean layered, hexagonal, and onion architectures, and provides practical guidance for effective system design.
Bounded ContextOnion Architectureclean architecture
0 likes · 9 min read

This article explains how to start a new project using Domain‑Driven Design, covering terminology, architecture evolution from monolith to microservices, bounded‑context definition, the four DDD boundaries, clean layered, hexagonal and onion architectures, and practical guidelines for effective system design.
Bounded ContextOnion Architectureclean architecture
0 likes · 9 min read

This article explains how to start a new project using Domain‑Driven Design, covering terminology, the evolution from SaaS to IaaS, bounded‑context concepts and division rules, the four DDD boundaries, and how clean, hexagonal, and onion architectures realize these principles for scalable backend systems.
BackendBounded ContextOnion Architecture
0 likes · 9 min read

This article explains how to start a new project using Domain‑Driven Design, covering key terminology, architecture evolution from monolith to microservices, bounded context division, the four DDD boundaries, clean layered, hexagonal and onion architectures, and practical design guidelines for backend systems.
Onion Architecturebackend developmentclean architecture
0 likes · 10 min read

This article explains how to apply Domain-Driven Design (DDD) to a new project, detailing the evolution from monolithic to microservice architectures, the concepts of IaaS, PaaS, SaaS, bounded contexts, the four DDD boundaries, and clean, hexagonal, and onion architectural patterns.
Bounded ContextDDDOnion Architecture
0 likes · 9 min read

Onion Architecture, a DDD‑aligned design pattern, structures applications into concentric layers centered on the domain model, promoting loose coupling, testability, and technology‑agnostic core logic, while detailing principles, layer responsibilities, testing strategies, microservice applicability, modular packaging, and practical implementation considerations.
BackendOnion Architecturedomain-driven design
0 likes · 12 min read

This article explains the concept of software architecture, why it is essential, the responsibilities of architects, various architectural classifications, and introduces classic patterns such as layered, CQRS, hexagonal, onion, and the open‑source COLA framework with its design, extension, and specification guidelines.
COLA frameworkOnion Architecturecqrs
0 likes · 16 min read

The article explains how Domain‑Driven Design combined with Onion Architecture creates a flexible, maintainable, and testable backend system by organizing code into concentric layers that isolate business logic from external concerns, supporting microservices, modular packaging, and appropriate testing strategies.
Domain-Driven DesignOnion Architecturebackend development
0 likes · 12 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 Domain‑Driven Design combined with the Onion Architecture creates a flexible, maintainable backend by separating concerns into concentric layers, detailing principles, services, testing strategies, microservice applicability, and modular packaging to help developers build scalable, technology‑agnostic systems.
Onion Architecturebackend developmenttesting strategy
0 likes · 12 min read

This article explains how to start a new project using Domain‑Driven Design, describes the evolution from SaaS to PaaS to IaaS, introduces bounded contexts, the four‑layer DDD boundaries, and compares clean, hexagonal, and onion architectures for building maintainable backend systems.
BackendDDDOnion Architecture
0 likes · 9 min read

This article explains how to apply Domain‑Driven Design to a brand‑new project, covering key terminology, architectural evolution, bounded contexts, DDD's four‑layer boundaries, and various layered architectures such as clean, hexagonal, and onion designs.
Onion Architecture
0 likes · 10 min read

This article explains the fundamentals of software architecture, why architecture is needed, the responsibilities of architects, various architecture categories, common styles such as layered, CQRS, hexagonal and onion architectures, and introduces the open‑source COLA framework with its layered design, extension points and standards.
COLA frameworkOnion Architecturecqrs
0 likes · 12 min read

This article explains the definition and necessity of software architecture, outlines various architectural categories such as business, application, distributed, data, physical, and operations architectures, describes layered, CQRS, hexagonal and onion models, and introduces the COLA framework with its design principles and extension mechanisms.
COLAOnion Architecturecqrs
0 likes · 12 min read

This article explains the meaning of architecture, why it is essential for any system, the responsibilities of architects, various software architecture classifications, common patterns such as layered, CQRS, hexagonal and onion architectures, and introduces the open‑source COLA framework with its layered, extension, and standard design principles.
COLA frameworkOnion Architecturecqrs
0 likes · 15 min read

This article explains the concept of software architecture, why it is needed, the responsibilities of architects, various architectural styles such as layered, hexagonal, onion, and introduces the COLA application architecture with its design principles, extension points, and CQRS separation.
COLAOnion Architecturecqrs
0 likes · 16 min read

This article explains the definition of architecture, why it matters, the role of architects, various software architecture classifications, layered designs, and key patterns such as CQRS, hexagonal, onion, and the COLA framework, providing a comprehensive guide for building maintainable systems.
COLA frameworkOnion Architecturecqrs
0 likes · 15 min read

This article explains the definition of software architecture, why it is needed, the responsibilities of architects, various architectural styles such as layered, CQRS, hexagonal, onion, and the COLA framework, providing a comprehensive overview for developers and system designers.
Onion Architecturecqrsdesign patterns
0 likes · 15 min read

This article explains what software architecture is, why it is needed, the responsibilities of architects, various classification types such as business, application, distributed, data, physical and operations, and introduces typical architectural styles like layered, CQRS, hexagonal, onion, and the open‑source COLA framework.
COLAOnion Architecturecqrs
0 likes · 13 min read

This article explains what software architecture is, why it is essential, the responsibilities of architects, various architecture classifications, common patterns such as layered, CQRS, hexagonal and onion designs, and introduces the open‑source COLA framework with its layered structure, extension mechanisms, and normative guidelines.
COLA frameworkOnion Architecturedesign patterns
0 likes · 13 min read

This article explains the fundamental notion of software architecture, why it is needed, the responsibilities of architects, various architecture classifications, typical application architectures such as layered, CQRS, hexagonal and onion models, and introduces Alibaba's open‑source COLA framework with its layered design, extension mechanisms and standards.
COLAOnion Architecturecqrs
0 likes · 13 min read

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.
COLAOnion Architecturecqrs
0 likes · 12 min read

This article examines the chronic decay of a complex warehouse inbound/outbound system, analyzes its tangled business logic and chaotic architecture, and presents a domain‑driven design solution with onion architecture, CQRS, and practical implementation steps to achieve clearer boundaries, higher cohesion, and sustainable evolution.
DDDOnion Architecturearchitecture
0 likes · 15 min read

This article examines the chronic decay of a long‑standing warehouse inventory system, identifies its tangled business boundaries, chaotic architecture, and uncontrolled delivery efficiency, then presents a domain‑driven design solution with clear modeling, onion‑style layering, CQRS, and practical implementation steps to restore maintainability.
Onion Architecturebackend architecturecqrs
0 likes · 15 min read

This article examines typical Android development challenges such as lack of standard architecture, lifecycle management, and testing difficulties, and presents the Snowball onion architecture—an MVVM‑based, RxJava‑powered framework with reusable components, best‑practice guidelines, and a supporting xueqiu‑onion library.
AndroidBest PracticesMVVM
0 likes · 12 min read

This article explains the concept of Explicit Architecture, describing how core modules, tools, ports, adapters, and component organization combine hexagonal, onion, clean, and CQRS patterns to achieve a loosely‑coupled, highly‑cohesive software system suitable for both monolithic and micro‑service applications.
Onion Architectureclean architecturecqrs
0 likes · 22 min read


ITPUBDec 30, 2020 · Fundamentals
This article defines software architecture, explains why it is essential, outlines the architect's responsibilities, categorizes various architecture types, and details common patterns such as layered, CQRS, hexagonal, onion, and the open‑source COLA framework with its design and extension principles.
COLA frameworkOnion Architecturecqrs
0 likes · 15 min read

This article explains the concept of software architecture, why it is essential, the responsibilities of architects, various architecture classifications, and introduces practical application architectures such as layered, CQRS, hexagonal, onion, and the open‑source COLA framework, highlighting how separating business logic from technical details improves maintainability and scalability.
COLA frameworkOnion Architectureapplication design
0 likes · 16 min read

This article explains what software architecture is, why it is essential, the responsibilities of architects, various classification types, common patterns such as layered, CQRS, hexagonal and onion architectures, and introduces the open‑source COLA framework with its layered design, extension mechanisms, and specification rules.
COLAOnion Architecturecqrs
0 likes · 14 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

This article explains what software architecture is, why it is essential for any system, the responsibilities of architects, various architecture classifications, and introduces the COLA open‑source framework that combines layered, hexagonal, and onion architectures with CQRS and extensibility to separate business logic from technical details.
COLA frameworkOnion Architectureapplication design
0 likes · 14 min read
