The article walks through a real e‑commerce payment case, showing how Domain‑Driven Design models entities, uses two key questions to split responsibilities, and continuously evolves the model to accommodate discounts, VIP features, and new payment adapters, reducing code churn.
The article presents a real‑world case of a ride‑hailing system whose microservices became tangled, and shows how applying Domain‑Driven Design—through strategic design, a six‑step refactoring roadmap, tactical four‑layer architecture, and context mapping—can systematically restore clean, business‑driven services.
The article explains how to evolve a DDD‑based domain model into a cross‑system ontology that provides AI agents with unified facts, computable logic, and executable actions, using a six‑step process illustrated by a customer‑health‑score case and detailed governance practices.
This guide explains Domain‑Driven Design (DDD) and shows how to structure Spring Boot microservices by organizing code around business domains, detailing strategic and tactical concepts, package layouts, layer responsibilities, cross‑domain communication, comparisons with traditional layering, evolution steps, and common FAQs.
The article explains why solid architecture matters for Java projects, outlines seven mainstream architectural patterns—including layered, DDD, hexagonal, clean, CQRS, event‑driven, and microkernel—and provides a decision guide to help teams choose the most suitable approach based on complexity, experience, performance, and evolution needs.
This article explains how CQRS splits write operations that enforce business rules using domain models from read operations optimized for page performance, illustrates common pitfalls of mixing the two, and provides concrete Java code, SQL examples, migration steps, validation checklists, and best‑practice guidelines for implementing lightweight CQRS in a DDD‑based backend.
The article explains why cross‑aggregate business logic belongs in domain services, how domain events capture immutable business facts, and demonstrates practical Spring Boot implementations—including in‑process publishing, message‑queue integration, and the Outbox pattern—while highlighting pitfalls and verification techniques.
Learn how to tell whether a domain concept is an Entity or a Value Object by asking if its identity matters or only its attributes, see concrete examples with Money, Address and Order, understand immutable design, proper equals/hashCode implementation, and validation through unit tests.
This chapter explains how to strategically allocate modeling effort in a DDD project by distinguishing domains, subdomains, core, supporting, and generic subdomains, using the “Preferred Store” case to illustrate which areas merit detailed modeling and which can remain simple, ultimately guiding resource focus and decision‑making.
The article shows how a typical three‑layer OrderService accumulates scattered business rules, mixes technical details with domain logic, lacks clear boundaries, and diverges from business language, then explains how Domain‑Driven Design reorganizes code around aggregates and bounded contexts to solve these problems while outlining when DDD is unnecessary.
The article recounts a 12,000‑line UserService.java file, explains how the overly generic name masks multiple responsibilities, violates the single‑responsibility principle, and creates a distributed monolith, then shows how domain‑driven naming and bounded‑context splitting can restore clear architecture.
The article examines a payroll bug caused by exposing internal collections, then explains three immutable‑focused rules for aggregate roots—expose only through the root, keep each transaction to a single aggregate, and reference other aggregates by ID only—showing how proper design prevents consistency errors, performance loss, and concurrency conflicts in Spring Boot applications.
Facing a large version release that made the existing MVC three‑layer system hard to maintain, the author outlines the shortcomings of thin entity models, scattered service logic, and code bloat, then presents a DDD‑based four‑layer architecture with domain‑driven design, DIP, and CQRS to improve cohesion, reduce complexity, and support long‑term evolution.
The article explains how bounded contexts, defined by language boundaries rather than functional ones, guide the logical separation of a payroll system into distinct domains, illustrating the process with concrete terminology lists, ambiguity detection, authority mapping, code examples, and deployment‑agnostic module structures.
This article explains core architecture design principles—including layered, hexagonal, and COLA structures—covers cohesion and coupling types with evaluation criteria, presents practical strategies to reduce coupling, and details domain‑driven design concepts such as bounded contexts, aggregates, and repository patterns, all illustrated with concrete code examples and decision records.
The article shows how mismatched business and code vocabularies cause confusion, then guides readers through building a shared glossary, renaming domain objects and types in Java, and enforcing the conventions with a code‑review checklist to keep the ubiquitous language alive in the codebase.
The article explains why traditional three‑layer architectures let business logic bloat inside services, demonstrates the pitfalls of anemic domain models with a 7,000‑line SalaryService example, and shows how DDD’s rich domain model restores rule ownership and maintainability.
The article explains how architects can bridge high‑level platform diagrams and concrete implementation by using DDD‑based module functional diagrams that serve as prompts for AI code generation, avoiding low‑level detail while ensuring domain understanding guides development.
The article analyzes whether endorsement (policy changes) and policy management should reside in a single microservice or be split into two, weighing data consistency, cohesion, operational simplicity, scaling, deployment independence, fault isolation, team size, and compliance, and provides a concrete decision framework and split strategy.
The article clarifies that microservices are defined by business‑capability‑aligned, independently deployable services—not merely smaller services—detailing five core mechanisms, distributed‑system constraints, SOA comparison, and five common misconceptions.
The article explains that CQRS originates from CQS, separates command and query responsibilities, clarifies its relationship with Event Sourcing and DDD, debunks four common misconceptions, and shows how it trades complexity for freedom when write and read optimizations conflict.
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.
The article compares the classic Event Sourcing + CQRS architecture with the more engineering‑focused read‑write separation CQRS, outlining their workflows, advantages, drawbacks, and guiding criteria for selecting the appropriate design in real‑world projects.
The article argues that Domain‑Driven Design is not an architectural style but a two‑layer framework—strategic design defines bounded contexts and ubiquitous language, while tactical design supplies the modeling tools—explaining common misreadings and showing how DDD complements Clean, Hexagonal, CQRS, and Event Sourcing approaches.
The article explains that software architecture is fundamentally about trade‑offs, categorises major architecture families such as DDD, Clean/Hexagonal/Onion, Microservices vs SOA, CQRS/Event Sourcing, MVC, PACELC, BASE, FLP, Repository and 12‑Factor principles, and shows how each addresses specific constraints to help engineers pick the most suitable design for their context.
The article explains how Domain‑Driven Design addresses the pitfalls of bloated services, unclear boundaries, and inconsistent terminology by introducing bounded contexts, aggregates, and domain events, and outlines a step‑by‑step adoption process while debunking common misconceptions.
The article examines whether services must adhere to strict layered calls in DDD, explains the layered‑to‑COLA refinement, describes the “sinkhole” anti‑pattern caused by excessive pass‑through interfaces, and offers criteria such as the 80‑20 rule for deciding when to open a layer.
The author recounts three years of applying Domain‑Driven Design to a microservice ecosystem, sharing concrete pitfalls, code‑first modeling from database tables, and a structured 24‑article series that guides developers to refactor existing Spring Boot + MyBatis Plus projects without rewriting the framework.
Domain-Driven Design (DDD) centers software architecture on business domains, breaking complex problems into clear subdomains, defining bounded contexts, ubiquitous language, and key building blocks such as entities, value objects, and aggregates, while guiding layered architecture and microservice decomposition for maintainable, collaborative systems.
This article explains why domain models are needed, walks through DDD's strategic and tactical design concepts, demonstrates a full knowledge‑payment platform case with bounded contexts, aggregates, and ubiquitous language, and outlines practical guidelines and limitations for applying DDD in real projects.
This article explores how to model clean, high‑cohesion Go structs using Domain‑Driven Design, value objects, entities, services, and proven patterns like functional options, builders, specifications, and repositories, illustrated with e‑commerce and payment system examples.
This guide shows how to break down tangled Java services using Domain‑Driven Design and Command‑Query Responsibility Segregation, providing concrete terminology, layered diagrams, code examples, and step‑by‑step migration strategies to improve maintainability, performance, and team communication.
The article explains why returning a generic Result wrapper from a Java service layer breaks responsibility separation, harms reusability, complicates exception handling and testing, and obscures transaction boundaries, advocating for returning pure domain objects instead.
The article explains that returning a Result wrapper from the Service layer mixes business logic with presentation concerns, leading to tighter coupling, reduced reusability, cumbersome error handling, harder testing, poorer DDD alignment, limited interface flexibility, and ambiguous transaction boundaries.
A three‑year‑old Java module riddled with technical debt was systematically refactored using AI tools, following a four‑stage plan of analysis, problem identification, solution design, and incremental implementation, while establishing rigorous verification to ensure safety and quality.
This article presents a detailed case study of using AI to assist domain‑driven design (DDD) for refactoring Taobao's monolithic flash‑sale service‑package system, showing how automated context extraction, code skeleton generation, and AI‑augmented implementation reduced development effort from 5‑8 person‑days to a configurable solution while improving architecture decoupling, code quality, and extensibility.
This article explains how hexagonal architecture serves as a solid foundation for gradually introducing domain‑driven design, outlines the stages of evolution, highlights common pitfalls, and provides concrete code examples to help teams decide when to move beyond hexagonal alone.
This article explains the fundamentals of Domain‑Driven Design, its core principles and two design phases, then shows how to apply DDD within a Spring Cloud Alibaba e‑commerce microservice system, providing a detailed layered architecture, file‑structure example, and recommendations for implementation.
This article examines how a rapidly growing Taobao flash‑sale service‑package system suffered from high development costs, duplicated code, and tight coupling, and shows how AI‑assisted domain‑driven design was applied to refactor the architecture, automate code generation, and dramatically improve efficiency, maintainability, and extensibility.
Using AI to assist domain-driven design, this case study details how a monolithic Taobao service-package system was analyzed, restructured, and refactored, reducing development effort from 5-8 person-days per package to configuration-based implementation while eliminating duplicated code and improving modularity, testability, and scalability.
The article explains how the COLA‑DDD layered architecture merges Clean Object‑Oriented and Layered Architecture with Domain‑Driven Design to eliminate large‑muddy code, improve iteration speed, enhance scalability, and provide clear layer boundaries, CQRS, event‑driven processing, and low‑risk technical evolution.
The article explains how a capacity‑driven microservice architecture uses performance metrics like QPS, TPS, and latency as the primary split criterion, detailing design principles, module responsibilities, and practical benefits that enable systems to handle traffic spikes without service collapse.
This article examines how early PHP developers often wrote tangled, procedural code that mixes business logic with presentation, and outlines concrete steps—adopting OOP, design patterns, domain‑driven design, test‑driven development, and modern tooling—to shift toward a cleaner, more maintainable backend development approach.
The article shares the author's practical frustrations with Domain‑Driven Design—covering confusing CQRS classifications, ambiguous aggregate‑root boundaries, performance conflicts, and the high time cost—while offering concrete examples, code snippets, and a candid conclusion that DDD should be applied judiciously rather than dogmatically.
This article explains what constitutes a complex system, defines software architecture, explores various architecture types, outlines key design factors, presents analysis methods like DDD, and reviews typical solutions such as microservices, cloud‑native, DevOps, and big‑data architectures for building robust, scalable systems.
Complex systems are composed of many interacting components, and understanding their architecture—from business and application layers to technical, data, microservice, cloud‑native, and DevOps designs—requires grasping core principles, requirements, and design patterns that ensure reliability, scalability, and long‑term value.
This article explores the essential role of modeling in software engineering, outlines the three main types of modeling, examines why modeling remains a persistent challenge due to language ambiguity and real‑world complexity, and provides practical guidance on business and domain modeling for architects.
The article explores core software architecture challenges through eight resonant concepts—big mud ball, independent value, domain division, concept design, classification perspective, domain thickness, global versus local, and scaffolding—offering practical strategies to avoid code chaos, clarify responsibilities, and foster engineering excellence.
After analyzing thousands of Chinese projects, the article reveals seven pervasive architecture design pitfalls—overreliance on frameworks, chasing trends, neglecting domain modeling, ignoring evolution, overlooking non‑functional requirements, lacking team standards, and weak testing—offering practical guidance to adopt business‑driven, scalable, maintainable designs.
This article explains how mastering business modeling, requirements analysis, and UML techniques—rather than focusing solely on code—helps developers create software that truly solves real business problems and drives profit, using lessons from the classic book “Software Method”.
This article explains how Event Storming—a collaborative, sticky‑note‑driven workshop—helps teams break down complex business processes into events, commands, aggregates and policies, dramatically speeding up requirements analysis, improving model quality, and turning the resulting model directly into code and living documentation.
This article explores the essence of software architecture, tracing its definition, its role in solving division‑of‑labor challenges, and how a pragmatic, balanced design that treats architecture as software design itself can deliver sustainable value while navigating business complexity, team coordination, and evolving requirements.
This article explains the fundamentals of hexagonal (ports‑and‑adapters) architecture, presents three ways to implement it in Spring Boot—including a classic version, a DDD‑enhanced version, and a simplified variant—while analyzing their advantages, disadvantages, and suitable scenarios.
This article explains how Domain‑Driven Design (DDD) complements microservice architecture by addressing functional partitioning gaps, guiding system decomposition, and improving scalability, while also highlighting common microservice pitfalls and practical steps for clear bounded‑context modeling.
This article introduces the fundamentals of Domain‑Driven Design (DDD), explains key concepts such as rich domain models, entities, value objects, aggregates, repositories, adapters, and application orchestration, and demonstrates their implementation through comprehensive Java code examples and a complete project structure diagram.
This article explains why overly fine‑grained service splitting hurts performance and debugging, shows best‑practice granularity aligned with team size, introduces evolutionary splitting based on model responsibilities, and walks through real‑world case studies, domain‑driven design concepts, architectural patterns such as hexagonal, CQRS, and event‑driven designs, and practical steps for building a robust service‑oriented system.
This article explains how the increasing complexity of business logic in modern backend systems leads to tangled code, and demonstrates how strategic and tactical Domain‑Driven Design (DDD) concepts—such as bounded contexts, aggregates, entities, value objects, repositories, and application services—can decouple business and technology, improve maintainability, extensibility, and stability, and guide practical layered architecture implementation.
This article shares a two‑and‑a‑half year effort to standardize code style and architecture across a large Java backend, detailing the origins, evolving patterns, a unified layered model, concrete implementation examples, measurable benefits, and future directions for continuous improvement.
Domain‑Driven Design (DDD) aligns software structure with business concepts by embedding rules in rich domain models, using aggregates, domain services, and events, contrasting with traditional anemic layers, and is ideal for complex, evolving domains such as e‑commerce, finance, or ERP systems.
This article explores how Domain‑Driven Design and hexagonal (clean) architecture were applied to Huolala’s user CRM, detailing the tactical design patterns, module breakdown, code examples, and the step‑by‑step migration that improved scalability, maintainability, and development efficiency.
This article explains Domain-Driven Design (DDD), contrasting it with traditional layered development through clear examples, outlines key DDD building blocks such as aggregate roots, domain services, and events, and discusses when DDD is appropriate for complex, frequently changing business domains.
The article explains that while encapsulation, inheritance, and polymorphism are often highlighted, true software craftsmanship hinges on the ability to abstract—identifying essential features, discarding irrelevant details, and modeling problem domains through steps like analysis, concept extraction, and system design, supported by principles such as low coupling, high cohesion, sufficiency, and completeness.
The article explains why developers must combine deep business understanding with AI tools, outlines a three‑layer domain model (core, generic, supporting), debunks common misconceptions, and provides a step‑by‑step methodology for mastering banking business concepts to boost ROI and career resilience.
The article explains how Domain‑Driven Design combined with microservice architecture can restructure a monolithic transaction system by defining bounded contexts, applying patterns such as layered architecture, CQRS and event‑driven communication, and refactoring domains to improve maintainability, scalability, and business clarity.
The article explains the DDD rich (or active) model, its core characteristics, compares it with the anemic model, and shows how to apply it in a shared‑rental billing domain using Java, DDD layers, domain events, and a lightweight framework.
This article discusses why and how to split monolithic applications into microservices, outlining common pitfalls of over‑splitting and presenting practical principles such as team and domain isolation, the three‑person rule, read/write separation, dependency management, and service count guidelines.
This article compares Domain‑Driven Design and MVC, outlines the architectural changes such as dependency inversion and layer separation, examines common drawbacks in real projects, and offers concrete guidance on when to adopt DDD, blend it with MVC, or stick to a lightweight CRUD‑centric approach.
This article explores the practical application of Domain‑Driven Design and hexagonal architecture in a real‑world CRM system, detailing strategic and tactical design, module division, code examples, and a step‑by‑step migration from a traditional layered architecture to a more flexible, maintainable backend solution.
The article proposes a domain‑model‑driven code paradigm—defining clear business models, core domain objects, and infrastructure abstractions like repositories, facades, and factories—while contrasting it with process‑driven designs using ability nodes and chains, arguing that these patterns cut repetitive effort and boost maintainability.
This comprehensive guide walks readers through the entire system design process, covering problem definition, key concepts, system analysis, modeling techniques, architectural thinking, design tools, requirements gathering, domain‑driven and use‑case modeling, design principles, patterns, and practical architecture delivery.
The team concluded that adopting Domain‑Driven Design can be valuable, but only when a company can afford the upfront investment, has a shared language and cross‑department collaboration, possesses strong OOP expertise, and maintains a culture supportive of the required organizational change.
This article provides a comprehensive overview of Domain-Driven Design (DDD), explaining its core principles, layered architecture, domain model components such as entities, value objects, aggregates, and bounded contexts, and includes Java code examples to illustrate implementation.
This article shares Ant Group's practical experience and evolution of data architecture, covering theoretical foundations, analysis of current challenges, proposed upgrade solutions based on domain‑driven design, and future outlook through complex network theory to improve scalability, governance, and resilience of large‑scale data systems.
This article provides a comprehensive introduction to Domain‑Driven Design (DDD), covering its origins, core principles, layered architecture, key concepts such as entities, value objects, aggregates, bounded contexts, and how DDD improves communication and maintainability in complex software systems.
This article details the step‑by‑step architectural evolution that merged retail and catering product systems into a shared, extensible platform using domain‑driven design, service standardization, and incremental vertical and horizontal upgrades to reduce technical debt and improve scalability.
This article explains how Meituan Dianping’s transaction platform evolved through three architectural stages—simple monolith, micro‑service, and platform—by adopting Domain‑Driven Design concepts such as ubiquitous language, bounded contexts, and iterative modeling to manage growing business complexity and improve system maintainability.
This article shares a recent graduate's journey into backend development at JD, offering practical advice for newcomers, detailing a large‑scale system refactor using domain‑driven design, discussing the creation of an AI‑powered merchant assistant, and emphasizing continuous learning and professional growth.
The article presents a real‑world case of a multi‑tenant system whose business logic was tightly coupled across tenants, leading to a massive service class, and demonstrates how applying Domain‑Driven Design, the Dependency Inversion Principle, and the Factory pattern can restructure the code into isolated tenant‑specific actions, improving maintainability and testability.
This article examines Ctrip’s evolution of its account system—from a monolithic service to a domain‑driven, middle‑platform architecture with multi‑region deployment—detailing the motivations, domain restructuring, read/write comparison process, configuration‑driven capabilities, and routing strategies that enable scalable, reliable user management.
Domain‑Driven Design (DDD) structures software around a rich domain model—entities, value objects, aggregates, and services—organized into UI, application, domain, and infrastructure layers, employing patterns such as aggregate roots, domain events, and event‑driven microservices to improve maintainability, scalability, and collaboration between developers and domain experts.
This article outlines the step‑by‑step architectural evolution of JD's advertising platform, describing how the system progressed from a simple, tightly coupled codebase through context‑based designs to a domain‑driven, capability‑oriented architecture that improves extensibility, reuse, stability, and knowledge transfer.
This article chronicles the multi‑generation architectural evolution of JD's advertising platform, explaining why a good code architecture must be extensible, reusable, maintainable and stable, and describing how domain‑driven design, aggregates, and ability orchestration were introduced to solve the challenges of complex, multi‑scenario business requirements.
This article explains what software complexity means, how it is measured and classified, outlines the negative impacts of high business complexity, and presents concrete architectural, coding, and configuration techniques to reduce complexity and improve maintainability.
The article explains the concept and measurement of software complexity, its impact on development cost and stability, common causes in business systems, and presents a set of architectural, coding, and configuration practices—including domain splitting, layered design, clear commenting, and configurable rules—to effectively reduce and manage complexity.
The article analyses Daniel Jackson’s concept‑driven software design presented at the 2024 Global Software R&D Conference, relates it to domain‑driven design and business services, and demonstrates how AI‑augmented prompts can generate Java domain models and a Spring‑Boot RESTful API for order submission.
This article shares a recent graduate's three‑year journey at JD, offering practical advice for newcomers, detailing a large‑scale system redesign for a merchant conference, outlining promotion‑season preparation, and describing the development of an AI assistant while emphasizing continuous learning and professional mindset.
This article shares the author's experience of redesigning a microservice using Domain‑Driven Design, detailing a standardized layered architecture, directory structure, model conversions, common pitfalls, and practical recommendations to improve code clarity and testing efficiency.
This article explains how to apply Domain‑Driven Design in a Java backend project, detailing the responsibilities of each layer—domain, infrastructure, application, adapter, client, and start—along with practical code examples for a work‑order system.
The article explains why microservices have become a mainstream architectural style, outlines the problems of monolithic systems, presents core microservice characteristics, offers practical decomposition principles and patterns, compares microservices with monolith, distributed, serverless, SOA and service‑mesh architectures, and lists common technology stacks for implementation.
This article explains Domain-Driven Design (DDD), its key concepts such as bounded contexts, ubiquitous language, domain models and layered architecture, traces its evolution, highlights recent trends like Event Storming and CQRS, and draws parallels to technical team management practices for handling complexity, communication, iteration, and strategic focus.
Domain-Driven Design (DDD) is a software development methodology that bridges business and technology by defining clear domain models, improving communication, code quality, and handling complexity through layered architecture, with concrete C# examples of entities, value objects, aggregates, and domain services.
This article introduces Domain-Driven Design (DDD), explains its core concepts, benefits, and the four-layered DDD architecture—including UI, Application, Domain, and Infrastructure layers—while also offering resources for deeper study and interview preparation.
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 define clear service boundaries, handle communication, and balance consistency with availability.
This article explains how Domain-Driven Design (DDD) can be used to tackle the complexity of a B2B marketing system by detailing strategic design, tactical design, and code architecture practices, illustrating concept modeling, bounded contexts, aggregation roots, and layered architectures with real‑world examples and diagrams.
The article distills the book “Software Method,” outlining a disciplined approach that starts with industry‑specific business modeling—defining vision, use‑case and sequence diagrams, and improvement patterns—then moves to precise requirements gathering, detailed analysis class diagrams, and finally design, emphasizing that true software value comes from meeting real demand.
This article explores what software architecture means, distinguishes vertical and horizontal architects, outlines the essential skills and methodology for architects, and provides a step‑by‑step framework—from understanding requirements and quality attributes to modeling business and system domains—so anyone can develop an architect’s mindset.
This article explains how Meituan applied Domain‑Driven Design to build a scalable B‑side marketing platform, covering background challenges, core DDD concepts, strategic use‑case modeling, tactical code mapping, aggregation design, and practical architectural patterns for large‑scale systems.
The article explains software architecture concepts, the architect’s duties of extracting requirements, designing and implementing solutions, and presents methodologies such as the C4 model, 4+1 view and domain‑driven design, while outlining how to develop architectural thinking through study, practice, reflection and ongoing learning.
This article explains the fundamentals of Domain-Driven Design (DDD), covering unified language, model abstraction, problem decomposition, aggregation, domain events, and how DDD principles translate into microservice architectures with practical code examples.
This article walks through a complete Domain‑Driven Design case study using a restaurant example, covering domain analysis, unified language, domain division, service design, modeling, upstream/downstream relationships, layered architecture, microservice boundaries, and functional implementation to illustrate how business concepts map to software structures.
