This article describes the design, domain‑driven architecture, probability algorithms, extensibility mechanisms, concurrency controls, and management UI of a reusable lottery platform that supports high‑traffic promotional activities while ensuring configurability, anti‑cheat measures, and reliable data consistency.
This article explains the principles, types, and layer responsibilities of DDD layered architecture, compares it with traditional four‑layer and three‑layer designs, and shows how microservices can evolve by reorganizing aggregates and applying dependency inversion across UI, application, domain, and infrastructure layers.
This article explains DDD aggregates, aggregate roots, entities and value objects, shows how to model them with event‑storming, illustrates e‑commerce and insurance examples, discusses design principles such as small aggregates, consistency boundaries, and cross‑aggregate communication.
This article explains why value objects are essential in Domain‑Driven Design, outlines their defining characteristics, shows practical modeling examples, compares different implementation forms, and demonstrates how they can simplify database design while highlighting their advantages and pitfalls.
This article explains why entities are essential in domain‑driven design, how to define unique identifiers, ensure their stability, model entities in various states, and implement robust constructors with Java code examples and practical guidelines.
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 explains how to treat Domain‑Driven Design as code by leveraging ContextMapper's DSL to model strategic and tactical aspects, define subdomains, bounded contexts, context maps, and generate consistent documentation and code artifacts for microservice architectures.
The article explains how Domain‑Driven Design (DDD) complements microservice architecture by addressing functional partitioning, clarifying bounded contexts, and guiding service decomposition, while also highlighting microservices' shortcomings in handling requirement changes and offering practical guidelines for effective system splitting.
This article recounts SuNing’s step‑by‑step journey of designing and implementing a supply‑chain data middle platform, outlining its business rationale, DDD‑based domain modeling, layered system architecture, and practical deployment insights that illustrate how a tailored big‑data solution can enhance data services and governance.
EventStorming is a rapid, lightweight collaborative modeling practice that combines Gamestorming and Domain‑Driven Design to accelerate team learning and build shared domain models across technical and business contexts.
This tutorial walks through a complete Golang implementation of a food‑recommendation API using Domain‑Driven Design (DDD), covering the four DDD layers, entity and repository definitions, persistence setup with Gorm, application services, HTTP interfaces, middleware, and how to run the service.
This article reflects on the redesign of a high‑traffic transaction system, discussing the decision‑making process, programming paradigms, SOLID principles, domain‑driven design, component decomposition, and the evolution from simple state machines to flexible, maintainable backend architectures.
In this article, Meituan‑Dianping expert Mu Zongyan’s GIAC conference talk highlights that while Domain‑Driven Design has become popular with microservices, its true power lies in strategic design rather than rigid tactical patterns, urging architects to focus on broader business contexts.
This article explains the core concepts of Domain‑Driven Design, including model‑driven design, ubiquitous language, bounded contexts, layered and hexagonal architectures, and key building blocks such as entities, value objects, aggregates, repositories, factories, and services, to help developers build business‑centric enterprise applications.
This article walks through the complete design of an e‑commerce microservice architecture, covering module identification, domain‑driven design, service splitting, technology stack choices between Dubbo and Spring Cloud, distributed transaction patterns, resilience with Hystrix, centralized configuration, and observability with SkyWalking.
This article examines the challenges of traditional retail accounting, introduces the concept of a financial middle platform, outlines its business and application architecture using the C4 model, and provides practical guidance for evolving the design into a micro‑service ecosystem while balancing complexity and performance.
This article details how applying Domain‑Driven Design to a complex e‑commerce discount system clarified business logic, improved flexibility, and guided a step‑by‑step architectural overhaul from a monolithic model to a layered, domain‑centric solution with tactical and strategic design considerations.
This article walks through building an e‑commerce platform using microservices, covering module decomposition, domain‑driven design, service splitting, technology stack choices, distributed transaction strategies, circuit‑breaker patterns, centralized configuration, monitoring, and capacity planning to guide developers from concept to deployment.
This article introduces Domain‑Driven Design, explains why traditional MVC‑based CRUD approaches lead to heavy, hard‑to‑maintain services, and shows how DDD concepts such as aggregates, bounded contexts, event sourcing and CQRS can clarify business logic, improve micro‑service boundaries, and reduce system complexity.
By applying micro‑frontend principles and DDD‑based microservice design, the article explains how insurance companies can build modular, reusable front‑end components that integrate with backend middle‑platform services, thereby lowering integration complexity, improving scalability, and enabling unified, cross‑product order sales across multiple channels.
This article explains what microservices truly are, debunks common misconceptions, outlines their key characteristics, discusses pitfalls such as over‑splitting into tiny monoliths, and highlights the importance of automated operations and DevOps practices for successful implementation.
EventStorming is a rapid, lightweight group modeling practice that accelerates shared domain understanding and domain‑driven design by using domain events, commands, bounded contexts, and collaborative workshops, making it applicable to any complex technical or business domain.
This tutorial walks through persisting Domain‑Driven Design aggregates by first explaining aggregates and aggregate roots, then showing Java class examples, followed by practical JPA/Hibernate integration challenges and a complete MongoDB document‑store solution, highlighting trade‑offs and best practices.
An extensive overview of JD.com's microservice component platform explains its underlying architecture, communication technologies, service mesh (ContainerMesh), design tools based on DDD, service evaluation, migration challenges, and the platform's evolution toward a cloud‑native, self‑evolving ecosystem supporting distributed tracing, API gateways, and plugin‑based development.
The article details how JD.com’s 7Fresh retail platform was built in just two and a half months by applying strategic DDD, virtual organization structures, extensive component reuse, and cross‑team collaboration to integrate over 60 systems and dozens of devices for both online and offline operations.
This article explains why domain modeling is crucial for managing complex business logic, compares transaction scripts with domain models using a bank transfer example, outlines the benefits of object‑oriented design, and provides practical steps and best practices for building, evolving, and visualizing domain models.
This article walks through a practical transformation of an old payment architecture into a high‑availability microservice ecosystem, covering SOA vs. microservices, DDD‑guided domain boundaries, Dubbo‑based implementation, operational challenges, continuous integration testing, and future plans for multi‑active data centers.
The article demonstrates how applying Domain‑Driven Design to a lottery platform’s microservices—by defining bounded contexts such as lottery and risk control, modeling aggregates like DrawLottery and AwardPool, using domain services and anti‑corruption layers, and enforcing high cohesion and low coupling—solves over‑coupling and anemic domain model challenges while tightly aligning the system with business logic.
Frank, a senior technical expert at Alibaba International, shares how his team tackled the growing complexity of their legacy CRM system by redesigning the architecture with extensible extension points, metadata, CQRS, DDD, SOLID principles, and disciplined layering to achieve better scalability, maintainability, and code readability.
The article explains how traditional microservice architectures evolve into event‑driven reactive microsystems by adopting events‑first DDD, reactive design, and event‑based persistence, highlighting the role of the Actor model, asynchronous non‑blocking communication, event sourcing, and saga‑based distributed transaction handling.
The article records a Meituan‑Dianping Q&A on Domain‑Driven Design, where engineers discuss using domain events with transactions, designing RPC interfaces, separating domain and application layers, handling cross‑aggregate operations, and defining bounded contexts, illustrating how DDD guides microservice architecture and business modeling.
This article explains the fundamental ideas of Domain‑Driven Design, showing how to build expressive domain models, use a ubiquitous language, map bounded contexts, apply strategic and tactical patterns, and implement the concepts with C# code, UML sketches, and architectural guidelines.
This article explains how to transform a classic layered monolithic architecture into microservices using Domain‑Driven Design, illustrates real‑world cases from Alibaba Cloud's EDAS platform, and shares practical best‑practice guidance on development, deployment, networking, and common microservice patterns.
This article explains how to split a classic layered architecture into microservices using Domain‑Driven Design, shares real‑world HSF/EDAS case studies, discusses deployment, operation, performance, and common microservice patterns, and offers practical best‑practice recommendations.
This article explains the appropriate use cases for the Factory pattern, details the responsibilities and characteristics of the application layer in SOA systems, and provides concrete C# code examples for services, DTOs, and data assemblers to illustrate clean separation of concerns and effective data transfer.
This article explores the definitions of SOA and DDD, explains DDD's layered architecture, demonstrates how business relationships become domain models, and provides concrete C# examples of repositories, services, and factories to illustrate the integration of service‑oriented architecture with domain‑driven design.
This article analyses the unique business complexity of China's 12306 railway ticketing system, proposes a domain‑driven aggregate design centered on the train route, explains how to model seat availability and ticket issuance, and outlines a CQRS/event‑sourcing architecture to achieve strong consistency and high concurrency.
This article chronicles a developer's five‑year journey of designing a system by starting with the business layer, exploring entities, repositories, services, view models, MVC, and tooling, while highlighting common pitfalls and practical solutions for backend architecture.
