1 views collected around this technical thread.
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.
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.
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.
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.
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.
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.
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.
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.
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.
This article explains how to start a new project using Domain‑Driven Design, introduces key terminology such as IAAS/PAAS/SAAS, describes the evolution of architecture through bounded contexts, and details the four DDD boundaries together with clean layered, hexagonal and onion architectures for building scalable backend systems.
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.
This article explains how to apply Domain-Driven Design (DDD) from project inception, covering terminology, architecture evolution across SaaS, PaaS, IaaS, bounded context division rules, the four-layer DDD boundaries, clean layered, hexagonal, and onion architectures, and concludes with practical insights for building decoupled, scalable systems.
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.
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.
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.
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.
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.
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.
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 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.