Tencent News upgraded its recommendation architecture by consolidating data platforms, redesigning index and feature services, adopting DDD and Lambda/Kappa patterns, and adding robust debugging and stability measures, which boosted availability to 99.99%, cut CPU, memory and cost by over 60%, and accelerated development and experiment cycles.
This article explains core Domain‑Driven Design concepts—entities, value objects, bounded contexts, aggregates, and aggregate roots—illustrates design principles with a WeChat transfer example, and provides TypeScript code snippets to show how to model and implement aggregates for robust backend systems.
This article explains Domain‑Driven Design (DDD) from its origins to practical modeling, compares it with MVC, outlines business and personal benefits, discusses drawbacks, details strategic and tactical concepts, and walks through a real‑world VOC product example using event‑storming and four‑color modeling.
This article shares hands‑on experience of applying Domain‑Driven Design in real projects, detailing a typical four‑layer architecture (domain, infrastructure, application, adapter), code examples, packaging guidelines, and practical tips for clean, maintainable backend systems.
Reflecting on his 2023 technical writings, the author—prompted by the TV series 'Reply 1988'—structures his insights into chapters covering Domain‑Driven Design lessons illustrated by a Forrest Gump metaphor, business‑architecture note‑taking, judgment models drawn from everyday driving, and personal projects like the VSEF framework and the “曲径通幽” series, emphasizing curiosity, knowledge sharing, and continual growth.
DataTester’s A/B testing platform underwent a comprehensive architectural overhaul, applying domain‑driven design, modular refactoring, automated validation, and dependency inversion to reduce change amplification, cognitive load, and unknown unknowns, ultimately improving code readability, maintainability, scalability, and development efficiency across its lifecycle.
The article explains Domain‑Driven Design’s philosophy of aligning business language with code, defines key concepts such as bounded contexts, entities, value objects, aggregates, and shows how these ideas translate into microservice decomposition, event‑driven integration, and reduced coupling for cloud‑native systems.
The article explains how business complexity and maintenance pain points can be mitigated by adopting Domain‑Driven Design, strategic and tactical patterns, hexagonal architecture, and a well‑structured microservice framework—illustrated with Go code examples and practical migration steps for large‑scale systems.
This article explains how to lower the learning curve of DDD and CQRS by using structured, standardized, and templated approaches, introduces a Maven archetype for rapid project scaffolding, and demonstrates an IntelliJ IDEA plugin that auto‑generates boilerplate code for aggregate roots, commands, queries, and related components.
This article examines the challenges of a legacy MVC‑based retail product system, explains why a shift to Domain‑Driven Design improves flexibility and scalability, and outlines concrete architectural and data‑model optimizations for robust backend development.
This article explores the fundamentals of Domain‑Driven Design, its challenges, practical steps for applying DDD concepts such as value objects, repository patterns, hexagonal architecture, and domain layer design, and shares concrete refactoring experiences to build more maintainable, extensible, and testable systems.
Domain-Driven Design (DDD) is a software design methodology that simplifies complex business domains by defining clear boundaries, layers, and core concepts such as aggregates, entities, value objects, and bounded contexts, helping teams achieve better business understanding, modularity, maintainability, and efficient architecture.
This article explains why legacy MVC codebases become tangled, introduces the domain‑driven design (DDD) layered architecture, and provides a step‑by‑step, low‑cost migration path—including layer mapping, call‑chain illustration, common pitfalls, and a concrete refactoring example with design patterns and code snippets.
This article explains Domain-Driven Design (DDD), its purpose, core concepts, layered architecture, and practical application scenarios, showing how DDD reduces business complexity, improves extensibility, and promotes reusable, maintainable code in backend systems.
This article presents a comprehensive case study of applying domain‑driven design, layered architecture, and microservice decomposition to a restaurant scenario, detailing domain analysis, modeling, upstream‑downstream relationships, architectural mapping, and functional design to guide backend developers in building maintainable systems.
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.
The article explains how business and domain modeling—using UML diagrams, RUP‑based workflows, and DDD principles—help engineers bridge the gap between business problems and technical solutions, enabling clearer requirements, stakeholder alignment, and improved system design across complex industries such as finance, logistics, and e‑commerce.
This article walks through the practical application of Domain‑Driven Design to a large‑scale pricing system, detailing business understanding, strategic and tactical design, context integration, layered architecture, and concrete Java implementations that illustrate how DDD improves modularity, testability, and maintainability.
This article explains the limitations of traditional MVC, introduces the four‑layer DDD architecture (Interface, Application, Domain, Infrastructure), discusses the Dependency Inversion Principle, compares package‑level and Maven‑module implementations, and details the roles and conversions of Entity, DO, and DTO models for Java projects.
This article explains how to combine Domain‑Driven Design's four‑layer architecture with a microservice‑oriented application SDK, introduces the D3boot lightweight framework and its modular base components, and shows how the approach simplifies building SaaS and PaaS systems while keeping code reusable and maintainable.
This article explains how Domain‑Driven Design (DDD) combined with Spring Data JPA enables clean, object‑oriented modeling of order workflows, introduces the Repository pattern for persistence, and demonstrates the full lifecycle—from creation to address modification and payment—through concise Java code and SQL examples.
This article explores Domain‑Driven Design fundamentals, illustrating how to expose hidden concepts, adopt hexagonal architecture, and implement repository patterns to achieve high scalability, maintainability, and testability in complex software systems, while addressing common pitfalls like the anemic model.
Domain-Driven Design (DDD) is a methodology for tackling software complexity by aligning business, system, and organizational structures through strategic and tactical modeling, using techniques such as metaphors, layering, refinement, abstraction, bounded contexts, and a ubiquitous language, illustrated with real-world Tencent video system case studies.
This article explains how Domain-Driven Design (DDD) rose to prominence by addressing the difficulty of defining business boundaries in microservice architectures, outlines the evolution of software architectures, describes DDD's strategic and tactical design concepts, and provides practical steps for applying DDD to create well‑bounded, high‑cohesion services.
This article explains Domain-Driven Design as a methodological approach for handling software complexity by aligning business, system, and organizational structures through modeling, detailing its core concepts, goals, key methods, and real‑world case studies from large‑scale systems.
This article shares practical experiences and detailed technical solutions for applying Domain‑Driven Design, Clean (Onion) Architecture, CQRS, and Saga patterns in backend systems, covering theory recap, modeling methods, module separation, code examples, and distributed transaction strategies.
The article walks through a DDD‑inspired four‑layer microservice architecture, explains how an application SDK enables RPC communication across services, details each architectural layer, and showcases the open‑source D3boot framework that bundles reusable base components, BOM management, and SaaS‑ready features for rapid backend development.
The article explains clean, hexagonal, and DDD layered architectures, detailing each layer’s responsibilities, principles, and evolution, and shows how DDD layering enhances microservice design, promotes strict separation, supports architectural evolution, and guides the transition from traditional three‑tier systems to modern domain‑driven microservices.
This article analyses how Domain‑Driven Design and a systematic architecture‑mapping process were applied to the Tencent Video “together‑watch” service, presenting concrete domain models, architectural decisions, refactoring steps, and quantitative evaluations—including code‑size reduction, performance gains, and cost savings—while preserving the full analytical reasoning behind each choice.
EventStorming is a rapid, lightweight group modeling technique that accelerates domain understanding by having cross‑functional teams collaboratively identify domain events, commands, aggregates, and bounded contexts, enabling faster, shared domain models and reducing reliance on individual DDD expertise.
This article explains why software architecture matters, defines the essence of Clean Architecture, compares it with Hexagonal and DDD layered models, and walks through a practical, step‑by‑step process—from business analysis and domain modeling to layer implementation and code examples—showing how to reduce complexity and maintenance cost.
This article provides direct links to a comprehensive DDD lecture series covering domain primitives, architectural fundamentals, the repository pattern, and best practices for designing a robust domain‑driven design in their projects, offering developers practical examples and essential guidance for implementing effective domain‑driven design.
This article presents a comprehensive set of software engineering principles—including obsessive code detail, entropy control, test‑driven design, domain‑driven modeling, and disciplined coding habits—to improve code quality, maintainability, and team collaboration across development projects.
The article expands on prior reflections by urging engineers to adopt a paranoid, entropy‑controlling mindset, design for testability, apply domain‑driven design, keep frameworks peripheral, enforce purposeful encapsulation and explicitness, and treat code as a craft, inviting community discussion.
This article comprehensively discusses the essential aspects of constructing a system engineering architecture, emphasizing value‑first decision making, layered and DDD architectural patterns, technology selection criteria, exception handling, logging, monitoring, and the importance of establishing shared consensus among teams.
This article explains how Volcano Engine identified the tangled authorization, data‑fetching, and performance problems of its advertising AB‑testing platform and refactored it by splitting services, redesigning the data model with MySQL and ClickHouse, applying DAG scheduling, time‑wheel algorithms, Domain‑Driven Design, and rigorous unit testing to achieve a more stable, extensible backend solution.
Rich (or active) models embed behavior and aggregation relationships directly within DDD entities, contrasting with anemic models; this approach clarifies business logic, reduces glue code, and improves readability, though it can cause entity bloat, prompting strategies like external service classes, utility helpers, and careful injection handling.
This article explores how to build a highly flexible and reliable retail product system by applying domain‑driven design, decomposing complex business logic into reusable components, orchestrating them, and employing a layered DDD architecture to handle diverse B2B and B2C requirements.
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 introduces a DDD scaffolding project, explains its theoretical foundations, presents the layered architecture and generation commands, details coding conventions for each module, and addresses frequent questions and solutions for practical adoption.
This article explains the concepts, strategic and tactical designs, layered architecture, key objects, aggregates, bounded contexts, and implementation steps of Domain-Driven Design (DDD) and how it guides the modeling and decomposition of microservices and middle‑platform systems.
This article explains the traditional strict and loose layered architectures, highlights their coupling issues, introduces the Dependency Inversion Principle as a solution, and shows how applying it leads to hexagonal and clean architecture designs with illustrative diagrams and code examples.
This article explores the challenges of retail product systems and presents a domain‑driven design approach, detailing the “Dao” (strategic planning) and “Shu” (technical tactics) of architecture, the divide‑and‑conquer plus orchestration strategy, abstract domain models, layered DDD structure, and data flow management to achieve a flexible, resilient solution.
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 article provides a systematic overview of Domain-Driven Design, explaining its origins, core concepts, modeling principles, strategic and tactical design steps, service decomposition patterns, and practical recommendations for applying DDD in complex backend systems.
The article likens blind adoption of Domain‑Driven Design to Forrest Gump’s run, explains how tangled business logic and over‑abstracted layers increase maintenance, shows DDD’s role in clarifying domains and mapping SOLID principles, offers practical tips for splitting responsibilities and building reusable capabilities, and concludes DDD is a valuable—not magical—lens for sustainable, extensible software.
This article walks through the historical evolution of backend architecture—from early N‑layered designs, through DDD, Hexagonal, Onion, and finally Clean Architecture—explaining why each style emerged, how they differ, and what practical rules developers can follow to manage complexity and dependencies.
This article explores engineering architecture design, emphasizing value‑first decision making, layered and DDD architectures, technology selection criteria, and best practices for consensus, exception, logging, and monitoring to build scalable, maintainable, and secure software systems.
This article surveys recent front‑end advancements, covering stunning CSS 3D image effects, design‑system construction, the high‑performance leaferjs canvas engine, Chrome 115’s new capabilities, TypeScript’s typechat project, npm ecosystem insights, DDD practices in information services, and an overview of a leading front‑end team.
This article provides a systematic overview of Domain-Driven Design, explaining its origins, core concepts, modeling approaches, strategic and tactical design steps, service decomposition principles, and practical examples to help developers understand and apply DDD in complex software projects.
This article explores the principles of engineering architecture design, emphasizing value‑first decision making, discusses common pitfalls, outlines layered and domain‑driven design patterns, compares MVC and hexagonal architectures, and provides practical guidance on technology selection, risk assessment, and operational best practices for building maintainable, scalable backend systems.
The article examines how applying the open‑closed principle and domain‑driven design in software architecture can lower programmers' cognitive load, streamline development, and enable cost‑effective, scalable evolution of complex systems, especially in fast‑iteration internet services.
This article explains how to start a new project using Domain‑Driven Design, covering key terminology, architecture evolution, bounded contexts, the four DDD boundaries, and common architectural styles such as clean layered, hexagonal, and onion architectures.
The article explains how Bilibili’s senior engineer uses Domain‑Driven Design combined with hexagonal architecture to merge separate VOD and live‑stream Danmaku services into a unified platform, detailing sub‑domain decomposition, six‑sided ports, rich models, mapping logic, and the trade‑offs of improved modularity, maintainability, and reduced duplication versus added design and refactoring effort.
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 (DDD), covering service terminology, architectural evolution from monolith to microservices, bounded contexts, the four DDD boundaries, clean layered, hexagonal, and onion architectures, and their practical benefits for backend systems.
This article explores Test‑Driven Development (TDD), explaining its core concepts, common misconceptions, tool choices such as JUnit, Mockito and JaCoCo, and provides practical case studies including a simple calculator and layered architecture examples in both anemic and DDD models.
This article starts from a conventional three‑layer architecture, refines it into a domain‑driven design (DDD) application structure, demonstrates the evolution through five concrete steps, and shows how to package the final architecture as a reusable Maven Archetype with detailed installation and usage instructions.
This article presents a comprehensive case study of the SPA system used by Qunar, detailing its business and technical complexity, the adoption of Domain‑Driven Design and an adapter‑based architecture, the migration to Spring WebFlux for reactive asynchronous processing, and the measurable improvements achieved after refactoring.
This article explains the fundamentals of Test‑Driven Development (TDD), highlights common misconceptions, guides tool selection, and walks through a complete Java TDD case study—including a strange calculator example, multi‑iteration refactoring, and DDD‑based testing—showing how to improve code quality and maintainability.
This article explains how Domain‑Driven Design (DDD) can be applied to a complex pricing system, covering business understanding, strategic and tactical design, context integration, layered architecture, code organization, and concrete Java examples that illustrate evaluation and pricing algorithms.
This article, the final installment of a DDD series, walks through a practical implementation of Domain‑Driven Design in Go using Kitex and Thrift, covering bounded contexts, layered architecture, domain modeling, persistence, factories, domain services, and cross‑cutting concerns in a fictional e‑commerce system.
This article guides you through refining a classic three‑layer architecture into a domain‑driven design, structuring the project with Maven Archetype, and implementing a simple CMS with both backend (Spring Boot) and frontend (Vue) components, complete with step‑by‑step setup instructions.
The article explains that architecture design exists to manage software system complexity, outlines common misconceptions, describes the six sources of complexity and their generic solutions, examines performance, availability, scalability, cost, security and scale concerns, and shows how microservices and Domain‑Driven Design can address these challenges.
This article introduces the core concepts of Domain‑Driven Design, demonstrates strategic and tactical modeling using a fictional "Smart Classroom" business, walks through event‑storming and four‑color modeling techniques, and provides a complete architectural and code‑level implementation guide for building a micro‑service‑based knowledge‑payment system.
Bilibili redesigned its fragmented account system into a unified, multi-tenant architecture using DDD and a four-layer design, consolidating all business lines into one codebase with configurable data isolation, logic, and dependencies, split into four micro-services, and migrated safely via gray-release and bidirectional sync.
In this interview, Qunar’s Vice President of Technology Zhang Yu shares how the company’s tech team has driven business growth over 18 years through DDD‑based system redesign, rapid container migration, digitalization of key technical metrics, and the establishment of the ITCP alliance to foster industry collaboration and build a strong technology brand.
The article defines software architecture as a business‑driven abstraction of system structure, explains core design principles such as SOLID, Ockham’s Razor, DRY, YAGNI, KISS and POLA, illustrates LSP violations, surveys layered, hexagonal, onion and DDD styles, and shows how applying Dependency Inversion in a large C++ codebase yields a simple, maintainable, business‑aligned architecture.
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 the author applied Domain‑Driven Design to build a microservice for an internal trading center, reviewing DDD strategic and tactical design, various architecture layer theories, a customized layered architecture, Maven module structure, and detailed responsibilities of each layer while sharing practical tips and challenges.
This article explains the concept of layered architecture for Java SpringBoot projects, introduces a nine‑layer structure, discusses each layer’s responsibilities, shows concrete code examples for utilities, infrastructure, domain, service, integration, facade, client, controller and boot modules, and summarizes the five design dimensions of single responsibility, noise reduction, adaptation, business logic, and data purity.
The article explores how AI‑driven prompt programming can transform traditional software development by converting natural‑language requirements directly into executable code, outlining its core features, DSL examples, DDD integration, practical demos, current challenges, and the future potential of real‑time software generation.
This article explains the definition of a domain in Domain‑Driven Design, its relationship with contexts, challenges of persisting aggregates, the debate over rich versus anemic models, and practical guidelines for clear layering and handling many‑to‑many relationships in backend systems.
This article explains the fundamentals of Domain‑Driven Design, covering its core ideas such as model‑driven design, ubiquitous language, bounded contexts, layered and hexagonal architectures, and key building blocks like entities, value objects, aggregates, repositories, factories, and services, with practical examples and diagrams.
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 explains what domain events are, how to define them with proper naming and attributes, explores multiple techniques for publishing events in Go—including parameter injection, static-like helpers, return‑based and repository‑based approaches—and describes strategies for consuming events safely and atomically.
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.
The article explains how to design large concurrent applications or refactor legacy systems using microservice architecture, covering decomposition by business capability and subdomain, distinguishing brownfield and greenfield projects, and addressing challenges such as network latency, data consistency, and the Strangler pattern.
This article provides an in-depth analysis of Remesh, a frontend framework implementing Domain-Driven Design (DDD) principles, exploring its core concepts, advantages, and practical implementation.
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.
This article explains how application services act as a façade for domain models, outlines key design principles, shows practical Go/Java implementation patterns, discusses transaction propagation and security handling, and provides concrete best‑practice recommendations for building thin, framework‑agnostic backend services.
This article explains how domain‑driven design (DDD) leverages object‑oriented principles and the Repository pattern, demonstrates integrating Spring Data JPA for persistence, and walks through a complete order lifecycle—including creation, address modification, and payment—showcasing lazy loading, automatic synchronization, and practical unit‑test examples.
This article explains Domain‑Driven Design fundamentals, covering how to define bounded contexts and subdomains, the criteria for domain division, practical modeling experiences, and detailed guidance on modeling entities and value objects with illustrative Go code examples.
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 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.
This article explains how introducing factories in Domain‑Driven Design with Go separates object creation logic from domain responsibilities, hides implementation details, enforces invariants, and improves validation, while showing practical code patterns and design‑pattern choices for simple and complex domain objects.
This article explains how Domain‑Driven Design can be used to split monolithic applications into well‑structured microservices by introducing strategic domain modeling, tactical design patterns such as aggregates and value objects, and provides a concrete Go project example with full directory layout and code snippets.
This article explains how Domain-Driven Design can be used to split monolithic systems into manageable microservices, covering DDD fundamentals, strategic domain modeling, tactical design patterns, and a concrete Go implementation with a four‑layer architecture.
This article explains how Domain-Driven Design (DDD) can guide the decomposition of monolithic applications into microservices by introducing strategic and tactical design concepts, illustrating them with a membership‑center example, and providing detailed Go code structures and implementations.
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 how Domain-Driven Design (DDD) complements microservice architecture by addressing functional decomposition, defining bounded contexts, and improving system evolution, while also highlighting common microservice pitfalls and practical guidelines for splitting complex systems.
This article explains the role of domain services in Go‑based Domain‑Driven Design, outlines three situations where they are appropriate, shows how to implement them statelessly, recommends functional package organization, and demonstrates dependency inversion with interfaces and infrastructure implementations.
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.
The article shows how Domain‑Driven Design can guide microservice decomposition by using strategic layers (core, supporting, generic domains) and tactical building blocks (aggregates, entities, value objects, services, events), illustrated with a membership‑center example and a four‑layer Go code architecture, while noting DDD’s suitability for complex domains.
This article explores the design and implementation of Fklang, a DDD‑guided architecture DSL, detailing its layered syntax, integration with IDEs, infrastructure abstractions, AI‑assisted code generation, mock server creation, and how it aims to industrialize software development through standardized modeling and tooling.
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 introduces a modular backend service architecture based on Domain-Driven Design, explaining project structure, module composition, hexagonal architecture, and practical code examples using Spring Cloud, illustrating how to achieve flexible, maintainable services through domain models, adapters, and proper boundary definitions.
This article explains how to construct a reusable base package for backend systems by defining Maven dependency guidelines, a unified response body with business codes, proper data object layers such as PO, BO, DTO, VO, and pagination utilities, while illustrating the concepts with concrete Java code examples.
This article details how a large‑scale project environment platform was refactored using domain‑driven design, distributed sharding, thread‑pool parallelism, second‑level scheduling, and distributed locks to achieve over 99% creation success, reduce creation time below 100 seconds, and keep exception rates under 1% despite massive task volume.
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.
