This article explains the fundamentals of Domain‑Driven Design, distinguishes strategic from tactical design, outlines core DDD elements such as domains, aggregates and bounded contexts, and demonstrates how four‑color modeling can be applied to real‑world e‑commerce microservice architectures.
This article walks through the author’s two‑year experience applying Domain‑Driven Design to payment, settlement and fund services, explains strategic vs tactical design, compares classic DDD layers, Clean, Hexagonal and Diamond architectures, details module organization, CQRS, and shares practical pros, cons and implementation tips.
This article explains how Domain‑Driven Design can guide the splitting of monolithic applications into well‑structured microservices by introducing DDD fundamentals, strategic domain modeling, tactical design patterns, and a concrete Go code example that demonstrates a four‑layer architecture.
The article explains the three core principles of Hexagonal (Ports‑and‑Adapters) Architecture, illustrates how to separate application, domain, and infrastructure code with concrete C# examples, and shows how this separation improves testability, dependency inversion, and modular design.
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.
This article explains the core concepts of Domain-Driven Design, why it is needed to address typical development problems, and how its strategic and tactical practices—such as bounded contexts, ubiquitous language, aggregates, and domain events—help teams build clearer, more maintainable software systems.
This article explains how to start a new project using Domain‑Driven Design, covering key terminology, the evolution of architecture layers, bounded context concepts, the four DDD boundaries, and various architectural styles such as clean layered, hexagonal, and onion architectures.
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 curates the ten most-read technical posts from NetEase Yanxuan in 2022, covering DDD adoption, reverse transaction systems, availability metrics, documentation practices, inventory locking, performance optimization, stability governance, H5 containerization, 2B architecture, and the evolution of the Yanxuan app’s engineering architecture.
This article describes how a data‑architecture team tackled the complexity of a large‑scale telephone‑robot system by adopting Domain‑Driven Design, detailing the challenges faced, the reasons for choosing DDD, the concrete rollout steps, and the resulting improvements in architecture, communication, documentation, and code quality.
This article presents a practical methodology for handling complex business scenarios by combining top‑down process decomposition with bottom‑up domain modeling, illustrating the approach with a retail product onboarding case, code examples, and guidance on capability sinking and model‑driven design.
This article explains how a WeChat team used Domain‑Driven Design to improve the maintainability, scalability, and stability of a fast‑paced, multi‑team e‑commerce project, covering strategic and tactical modeling, layered architecture, subdomains, bounded contexts, anti‑corruption layers, domain events, aggregates, repositories, and a practical code scaffold with C++ examples.
The article explains how a WeChat e‑commerce team adopted Domain‑Driven Design, reorganizing a fast‑paced, multi‑team project into a four‑layer onion architecture with strategic sub‑domains, bounded contexts, anti‑corruption layers, domain events, aggregates, repositories and services, to achieve maintainability, extensibility, cohesion and loose coupling.
This article explains a layered microservice architecture, detailing the responsibilities of Facade, Application, Domain, and Infrastructure services, the interaction patterns within and between services, strict versus loose layering, and the roles of various data objects such as PO, DO, DTO, and VO.
Amid sweeping layoffs in Silicon Valley and China, developers must shift from generic coding to specialized expertise by building irreplaceable core competencies, understanding true business knowledge, and applying domain‑driven design to stay valuable in a maturing market.
Business Knowledgedomain-driven designsoftware engineering
This article explains how Domain‑Driven Design (DDD) guides the strategic and tactical decomposition of monolithic applications into well‑bounded microservices, outlines its benefits such as a unified language and clearer domain boundaries, and provides concrete code examples from a membership‑center service.
This article examines the technical challenges of B‑end contract advertising systems, tracing the evolution of Baidu's ad‑placement platform from a monolithic architecture through multiple business stages to a domain‑driven microservices design, and discusses service governance, observability, anti‑corruption, and iterative development practices.
This article explains how to build a modular backend service in Java using domain‑driven design, configurable modules, dynamic proxies, cache adapters, lambda‑based query conditions, and Spring‑based conditional bean loading to enable flexible extensions without altering existing code.
The article examines Baidu's Contract Advertising Platform, detailing its shift from a monolithic, siloed design to a DDD‑driven microservices architecture using COLA, CQRS, and layered governance, and shares best practices for handling complex B2B advertising scenarios, service iteration, and evolving business needs.
This article explores the challenges of implementing Repository in Domain‑Driven Design, introduces the innovative “Repository Entity Transfer” concept, compares in‑memory and relational implementations, discusses concurrency, specifications, and architectural patterns, and provides practical code examples to help developers build cleaner, model‑centric back‑end systems.
This article walks through the complete process of designing a budget‑control platform using Domain‑Driven Design, covering background analysis, strategic and tactical design, domain modeling, service decomposition, interface definition, and technical implementation to illustrate how to build a cohesive, scalable backend service.
This article presents a comprehensive case study of how Qunar's hotel supply‑chain team applied Domain‑Driven Design to restructure a decade‑old, highly coupled hotel information system, detailing the problem analysis, DDD rationale, evolutionary transformation process, architectural principles, implementation results, and lessons learned.
The article explains why Domain-Driven Design (DDD) is valuable for handling complex business logic, compares it with traditional transaction‑script approaches, introduces core DDD concepts such as ubiquitous language, bounded contexts, entities, value objects, aggregates, factories, repositories and domain services, and provides practical steps and examples for adopting DDD in backend development.
This article explores how structured domain model metadata, derived from domain‑driven design principles, can standardize business component descriptions, enable visual UML modeling, support low‑code and no‑code generation, and ultimately reduce development costs while accelerating delivery of enterprise support systems.
This article explains why Domain‑Driven Design is needed, critiques traditional development workflows that produce opaque code, and presents various modeling and aggregation strategies—including code examples—to involve non‑developers and bridge the gap between business experts and developers.
This article explains how Domain‑Driven Design (DDD) differs from classic MVC layering, introduces core DDD terminology, compares anemic and rich domain models, and presents a practical multi‑layered DDD architecture with its concrete benefits for complex software systems.
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 explores the concept of software architecture, its relationship to business, key design principles such as SOLID and Ockham's razor, various architectural styles like layered, hexagonal, and onion, and illustrates how a real‑world navigation engine team applied domain‑driven design to restructure their codebase.
This article introduces the “individual‑ten‑hundred‑thousand” thinking framework, maps its four levels (digital transformation, strategy, governance, management) to Domain‑Driven Design, and explains how DDD principles, strategic design, team organization, and tactical design together support successful microservice and middle‑platform architectures.
This article explains the fundamentals of Domain‑Driven Design, compares it with traditional MVC, details layered architecture, data transformation objects, core concepts like aggregates and domain events, and provides a full Java SpringBoot DDD demo with code, project structure, database schema, and deployment steps.
The article details how NetEase Yanxuan applied Domain‑Driven Design to reconstruct its Product Center middle‑platform, using strategic and tactical design, COLA layered architecture, and an event‑driven mechanism to eliminate duplicated logic and heavy coupling, cutting code volume by roughly two‑thirds while addressing entity scope, model richness, and microservice granularity challenges.
This article explains how to translate complex Domain‑Driven Design concepts into concrete code structures, covering domain objects, application services, infrastructure, and context integration, and demonstrates the approach with a ticket‑service case study using Spring Boot and Spring Cloud Stream.
The article explains how software complexity arises from scale, structure, and change, and shows that controlling dependencies through bounded contexts and aggregates—by reducing dependency quantity and weakening dependency strength—provides a practical way to achieve high cohesion and low coupling in system architecture.
The article explains how software complexity stems from scale, structure, and change, and shows that controlling dependencies—by reducing their number and weakening their strength—through bounded contexts and aggregates is the key to achieving high cohesion and low coupling in domain‑driven design.
This article explains the origins of Domain‑Driven Design, describes strategic concepts such as domain, bounded context and context mapping, explores tactical building blocks like entities, value objects, services, aggregates and factories, and demonstrates practical architecture choices and Java code examples for a payment system.
In this interview, Meituan Selection architect Xu Po shares his 14‑year journey, explains how logistics architecture balances process and result quality, outlines the four pillars for successful architecture implementation, discusses the core value of architects, team organization models, essential skills, and the role of domain‑driven design.
This article explains how microservice architecture leverages Domain‑Driven Design concepts such as bounded contexts and aggregates, uses context mapping and Event Storming to define service boundaries, and discusses communication patterns, eventual consistency, and Backend‑for‑Frontend design to build resilient, loosely‑coupled distributed systems.
This article explains how Domain-Driven Design is applied to a hotel transaction platform, detailing a four‑layer loose DDD architecture, the responsibilities of each layer, code implementation examples, and strategies for maintaining consistency across aggregates using events and factories.
This article explains how microservice architecture differs from traditional service‑oriented designs, outlines its key characteristics, and shows how Domain‑Driven Design, bounded contexts, aggregates, context mapping, and event‑storming can be used to define clear service boundaries and build resilient, loosely‑coupled systems.
This article explores the concept of fully interface‑based domain modeling, demonstrates how to design domain objects as interfaces, shows repository implementations for JPA, MyBatis and Elasticsearch, discusses association handling, and explains how such designs enable seamless switching between monolithic, clustered and microservice deployments.
This article introduces Domain‑Driven Design, explaining its strategic and tactical aspects, core concepts such as bounded contexts, ubiquitous language, aggregates, entities, and value objects, and illustrates how DDD can be applied to complex business domains like hotel transaction systems.
This article walks through constructing a welfare‑center microservice using Domain‑Driven Design, detailing a four‑layer architecture, strict naming conventions for POJOs, method naming rules, code‑style guidelines, directory layout, and concrete Java examples for adapters, services, domain objects, and infrastructure components.
This article walks through Domain‑Driven Design fundamentals, distinguishes strategic and tactical design, introduces the four‑color modeling archetypes, and demonstrates their application in an e‑commerce microservice case study, highlighting how DDD bridges business requirements and code architecture.
This article explains how Airwallex uses Domain-Driven Design (DDD) to model a complex payment system, detailing strategic and tactical patterns, bounded contexts, domain events, and the translation of domain models into microservice architectures, while highlighting the benefits of clear communication and modular design.
This case study details how Qunar’s hotel pricing platform was reorganized in 2021 using Domain‑Driven Design and explicit architecture principles to streamline cross‑team collaboration, reduce data‑flow complexity, and improve response time by 25%, while aligning system structure with Conway’s Law.
In this interview, Qunar's technical director Zheng Jimin shares how the company revived Domain‑Driven Design to restructure hotel pricing, discusses strategic and tactical design, implementation challenges, success criteria, and the broader impact of technical influence on organizational growth.
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 why code quality often degrades despite clear requirements, introduces Domain‑Driven Design (DDD) and Algebraic Data Types (ADT) as a unified modeling approach, shows how Curry‑Howard isomorphism connects domain knowledge to type systems, and demonstrates practical TypeScript examples that reduce illegal states, defensive code and improve maintainability.
Type Theoryalgebraic data typesdomain-driven design
This article introduces Domain-Driven Design (DDD), explains key terminology, describes the evolution of architecture from SaaS to IaaS, details bounded context concepts and division rules, and reviews major architectural styles such as clean layered, hexagonal, and onion architectures for building robust software systems.
This guide walks through applying Domain‑Driven Design to a brand‑new project, covering essential terminology, the evolution from SaaS to IaaS, defining bounded contexts, the four DDD boundaries, and various architectural styles such as clean layered, hexagonal, and onion architectures, with practical insights for implementation.
This article explains Clean Architecture, shows how Domain‑Driven Design fits into its concentric‑layer model, and demonstrates how adding Command‑Query Responsibility Segregation (CQRS) enhances scalability, testability, and maintainability while outlining practical implementation steps, benefits, and trade‑offs.
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.
This article provides a comprehensive overview of Domain-Driven Design (DDD), explaining its principles, strategic and tactical design, layered architecture, key objects such as entities, value objects, aggregates, and how DDD guides microservice and platform development.
This article summarizes Evans' concise DDD booklet, explains why domain‑driven design is needed, outlines the problems it addresses, describes strategic and tactical design practices—including bounded contexts, ubiquitous language, aggregates, and event storming—and highlights common pitfalls and supporting tools.
This article explains Domain-Driven Design (DDD), outlining why it is needed, how it solves common software development problems, and detailing strategic and tactical design steps, event‑storming techniques, and common misconceptions to help teams align business and technical perspectives.
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.
This article explains how to design microservice architectures by applying domain‑driven design concepts such as bounded contexts and aggregates, using context mapping and event‑storming techniques to identify service boundaries, and discusses communication patterns, CAP trade‑offs, and the Backend‑for‑Frontend approach.
This article shares practical experience of using Domain‑Driven Design to refactor an e‑commerce product detail page, detailing domain decomposition, relationship‑network design, polymorphic logic handling, and two concrete case studies that illustrate how to support both online and offline sales scenarios with minimal impact on existing services.
Applying Domain‑Driven Design to Youzan’s Credit Core System involved consulting experts, mapping loan processes, using four‑color modeling to define documents, participants, roles and data, establishing bounded contexts, designing sub‑domains with use‑case diagrams, and adopting a layered (often hexagonal) architecture to ensure maintainable, scalable microservices.
This article explains why and when to break a monolithic application into microservices, outlines the business and technical signals that trigger splitting, presents guiding principles, functional and non‑functional strategies, and risk‑mitigation practices to ensure a smooth, sustainable migration.
This article explains the concepts of aggregates and aggregate roots in DDD, describes how to design aggregates through event storming with a concrete insurance underwriting example, and outlines key design principles and the relationships among aggregates, entities, and value objects.
This article explains the philosophical basis of object‑oriented thinking, distinguishes attributes and operations, compares data‑model and object‑model designs with Java and SQL examples, discusses composition versus aggregation through a digestion model, and illustrates application‑service patterns in account credit scenarios.
The article explains various context‑mapping techniques from Domain‑Driven Design—such as Partnership, Shared Kernel, Customer/Supplier, Conformist, Anti‑Corruption Layer, Open Host Service, and Published Language—and advises when to apply each based on code, team, and business considerations.
This article explains how mismatched vocabularies between domain experts and developers hinder project progress, and how establishing a shared, model‑driven language can reduce misunderstandings, streamline communication, and improve the reliability of software built with Domain‑Driven Design.
The article explains how mismatched vocabularies between domain experts and developers hinder project progress, and argues that establishing a shared, model‑driven language—central to Domain‑Driven Design—can improve communication, reduce misunderstandings, and create more reliable software.
The talk demonstrates how to apply Domain‑Driven Design and microservice architecture to an e‑commerce voucher platform by defining problem spaces and bounded contexts, prioritizing boundaries over aggregates, using layered‑on‑demand infrastructure, and following SOLID principles to achieve clear, maintainable services.
This article shares personal notes and a mind‑map on Domain‑Driven Design, explaining effective modeling elements, knowledge digestion, continuous learning, and deep modeling to help development teams build structured, collaborative domain models that align code with business logic.
This article shares eight months of hands‑on experience with Domain‑Driven Design, explaining why traditional waterfall approaches hinder true business understanding and presenting practical notes, mind‑map visualizations, and step‑by‑step guidance on effective modeling, knowledge digestion, continuous learning, and deep model design.
This article provides a comprehensive, practical guide to applying Domain‑Driven Design (DDD) in enterprise Java projects, covering architectural principles, project management steps, design patterns, code generation, testing, deployment, and a detailed loan‑processing example that demonstrates how to model, implement, and evolve a rich domain model using Spring, DI, AOP, and related technologies.
Anemic domain models separate data and behavior, leading to procedural code and maintenance challenges, while rich (or “充血”) models embed logic within objects, offering clearer OOP design, better encapsulation, and scalability, though they require careful design to avoid complexity.
The article explains the differences between the anemic (transaction‑script) and rich (domain‑model) approaches in DDD, discusses their historical origins, advantages, drawbacks, and provides guidance on when and how to apply each model in software design.
The article explains how to decompose a business problem into domains, subdomains, core, generic, and supporting domains by using a peach tree analogy, illustrating the steps and reasons for such classification in Domain‑Driven Design and microservice architecture.
This article explains how to design a robust e‑commerce shopping‑cart service by separating business, system, and technical architectures, applying DDD, strategy and chain‑of‑responsibility patterns, and choosing Redis data structures for high‑performance storage.
This article explains the fundamentals of Domain-Driven Design, covering its core concepts, step‑by‑step design methodology, domain modeling techniques, and how to apply DDD in microservice architectures with considerations for technical elements such as distributed transactions and scalability.
The article explains how Domain-Driven Design (DDD) rose to prominence by addressing business‑boundary challenges in microservice architectures, outlines the evolution of software architectures, and details DDD’s strategic and tactical design practices for creating clear, maintainable service boundaries.
The article explains the core traits of entities—identity and continuity—through domain‑driven design examples, demonstrates why a Message should be modeled as an entity, and discusses the reasoning behind treating Sender and Recipient as value objects or entities in a messaging domain.
This article explains how good software architecture enables easy evolution, fault tolerance, and low maintenance, while bad architecture leads to complexity and brittleness, and it outlines key principles, design styles, and practical techniques such as domain‑centric, microservices, event‑driven, and CQRS to build robust, adaptable systems.
This article provides a concise overview of Domain-Driven Design, explaining why it matters, defining key concepts such as domain, model, bounded context, and ubiquitous language, and illustrating how DDD helps teams tackle core software complexity through collaborative modeling and shared terminology.
This article explains the core characteristics of entities—identity and continuity—using domain‑driven design principles, analyzes why a Message should be modeled as an entity, and argues that senders and recipients are better represented as entities rather than value objects in a messaging system.
The article explains the core characteristics of entities—identity and continuity—using DDD concepts, demonstrates why a Message in a messaging scenario qualifies as an entity, and argues that senders and recipients (contacts) should also be modeled as entities rather than value objects.
This article explains how domain‑driven design, bounded contexts, context mapping, and event‑storming techniques can be used to identify, model, and communicate clear microservice boundaries, while also covering fault tolerance, eventual consistency, and backend‑for‑frontend patterns for robust distributed systems.
This article describes how Keep leveraged Domain‑Driven Design, hexagonal architecture, CQRS and EventStore to restructure a legacy supply‑chain system, solve inventory inaccuracies, improve modularity, and achieve scalable, maintainable backend services for its e‑commerce platform.
This article explains object‑oriented fundamentals, contrasts object and data models with Java and SQL examples, discusses application services, and clarifies composition versus aggregation through real‑world analogies and code demonstrations.
This article explains the philosophical basis of object‑oriented thinking, contrasts object models with data models using a simple account example, demonstrates how to design services and sequence diagrams, and clarifies the difference between composition and aggregation in software design.
This article presents a comprehensive overview of how a team applied Domain-Driven Design to migrate a car‑purchase invoice repository, detailing DDD fundamentals, strategic and tactical design phases, module architecture, coding standards, and lessons learned from the implementation.
This article explains the philosophical basis of object‑oriented thinking, distinguishes objects from things, discusses attributes and methods, compares object‑oriented and data‑model designs with Java and SQL examples, and clarifies composition and aggregation through real‑world and code illustrations.
The article explains the need for Domain‑Driven Design (DDD) to manage growing complexity caused by frequent requirement changes, describes DDD fundamentals such as bounded contexts and event storming, and shows how to structure React front‑end code, actions, reducers, and routing by organizing features to reduce coupling and improve maintainability.
This article introduces the essential principles of Domain‑Driven Design, explaining its two‑stage approach, key building blocks such as entities, value objects, aggregates, factories, repositories, services, and domain events, and shows how DDD fits into layered architecture and common anti‑patterns.
This article explains the core concepts, patterns, and architectural styles of Domain-Driven Design, covering model‑driven design, bounded contexts, layered and hexagonal architectures, building blocks such as entities, value objects, aggregates, repositories, factories, and services, with practical examples and diagrams.
This article explains how Domain‑Driven Design (DDD) gained popularity alongside microservices, outlines the evolution of software architectures, highlights the boundary‑defining problems of microservices, and shows how DDD’s strategic and tactical design methods help create clear, high‑cohesion, low‑coupling systems.
This article details the step‑by‑step architectural evolution of JD Daojia's product system—from the initial 1.0 monolithic design, through 2.0 high‑availability and performance enhancements, to the 3.0 domain‑driven microservice architecture—highlighting the motivations, technical solutions, and future outlook.
This article explores comprehensive domain interface design in Java backend development, showing how to model domain objects as interfaces, implement repositories for JPA, MyBatis, and Elasticsearch, handle associations with JPA annotations, and apply these patterns in the open‑source Mallfoundry e‑commerce platform.
Domain-Driven Design (DDD) focuses software development on deep domain understanding, offering a proven, timeless approach to tackling core complexity, especially in large or evolving systems, while emphasizing the crucial role of a well‑crafted domain model and DSL.
This article explains how Baidu’s AiFanFan team introduced Domain‑Driven Design to tackle complex enterprise‑level requirements, detailing the strategic and tactical steps, core DDD concepts, layered implementation, and the concrete benefits gained from adopting a domain‑centric architecture.
This article explains the fundamentals of Domain‑Driven Design (DDD), outlines its strategic and tactical design processes, and demonstrates how Haro’s transaction platform applies DDD across taxi, e‑commerce, and core trading scenarios, highlighting benefits, challenges, and practical recommendations.
This article explains how Domain‑Driven Design provides a systematic approach to modeling complex business domains, guiding microservice decomposition, service boundaries, bounded contexts, and layered architectures, while addressing software complexity through strategic and tactical patterns such as SOLID, aggregates, and hexagonal design.
The article explains how the thermodynamic entropy principle inspires software architecture design, emphasizes abstract thinking and domain‑driven design, compares monolithic and microservice approaches, outlines microservice benefits and distributed‑system design principles, and discusses the complementary role of middle‑platform architecture in modern backend development.
The article explains how software degradation occurs as systems evolve, why domain‑driven design combined with a two‑step refactoring approach can maintain high‑quality design, and demonstrates these concepts through an e‑commerce payment case study, covering principles like OCP, SRP, and micro‑services.