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.
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 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 free, four‑part kata lets participants practice architecture and domain‑driven design by creating a business model for a fictional online car dealership, exploring domain boundaries with event storming, aligning domains to strategy, and modeling message flows using commands, events, and queries.
This article explains how software engineers can systematically abstract real‑world problems into domain models, walk through four essential modeling steps, illustrate the process with multiple real‑world cases, and discuss advanced techniques such as event storming, four‑color modeling, and bounded‑context pen‑paper methods to create stable, extensible software designs.
This guide outlines practical steps and best‑practice recommendations for designing reusable, stable, and composable enterprise APIs, covering domain‑driven modeling, stakeholder collaboration, API specification creation, validation, tooling, and governance to ensure high‑quality, evolvable services.
This article details how Ctrip's car‑hailing and rental platforms tackled growing technical debt and system complexity by adopting Domain‑Driven Design, using event‑storming workshops, defining bounded contexts, and aligning team boundaries to improve maintainability, performance, and overall development efficiency.
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 explores how microservice architecture, guided by Domain‑Driven Design principles such as bounded contexts, aggregates, and context mapping, defines service boundaries, improves autonomy, and influences communication patterns, including event‑driven integration, synchronous APIs, and BFF strategies, while addressing consistency, scalability, and deployment challenges.
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.
The article explains microservices architecture, detailing its defining characteristics, the role of domain‑driven design and bounded contexts, how aggregates and context mapping help define service boundaries, and discusses communication patterns, eventual consistency, event‑storming, and the backend‑for‑frontend approach for building resilient, loosely‑coupled systems.
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 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 explains how to replace a traditional three‑tier architecture with a DDD‑based four‑layer microservice design for a welfare‑center system, detailing the advantages and drawbacks of each approach, the event‑storming process for domain modeling, and the construction of entities, aggregates, aggregate roots, domain events, and bounded contexts.
This article explains the principles of microservices architecture, the role of bounded contexts and domain‑driven design, and practical techniques such as context mapping, event storming, and BFF patterns for defining service boundaries, handling communication, and achieving resilient, loosely‑coupled systems.
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 explains how to break monolithic applications into domain‑driven microservices by defining clear bounded contexts, using aggregates, applying context‑mapping and event‑storming techniques, and choosing appropriate communication patterns such as asynchronous events, CAP trade‑offs, and BFF for frontend integration.
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 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 how to design microservice architectures by applying Domain‑Driven Design principles, defining bounded contexts and aggregates, using context mapping and event‑storming to identify service boundaries, and addressing communication, consistency, and orchestration challenges in distributed systems.
This article explains how microservice architectures differ from traditional service‑oriented designs, outlines key characteristics such as bounded contexts and autonomy, and shows how Domain‑Driven Design, context mapping, and event‑storming can be used to identify, model, and communicate clear service boundaries for resilient, scalable systems.
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.
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 explains how to design microservice architectures by applying domain‑driven design, defining bounded contexts, using context mapping and event‑storming techniques, and addressing communication, consistency, and integration patterns such as event‑driven messaging and the Backend‑for‑Frontend approach.
This article examines how Qunar’s technology director applied Domain‑Driven Design to reshape business processes, the challenges faced, tools used, and practical steps for teams to adopt DDD effectively in a large micro‑service environment.
This article explains how defining bounded contexts and establishing a ubiquitous language during event‑storming sessions ensures clear, consistent terminology that maps directly to domain objects and code, guiding accurate microservice design and implementation.
This article explores the communication gaps that hinder software projects, introduces Event Storming as a visual, collaborative workshop technique, walks through its syntax and practical coupon‑distribution example, connects the outcomes to Domain‑Driven Design, and shows how the method improves alignment between product, business, and engineering teams.
