Domain-Driven Design
A software design methodology that emphasizes aligning code naming conventions with business domain terminology. It introduces the concept of a Ubiquitous Language, ensuring that technical implementation and business logic are aligned at the linguistic level.
Core Facts
Timeline (last 90 days)
The first layer of legacy system refactoring requires systematic decomposition using domain-driven design (DDD), defining clear bounded contexts, and refactoring business domains into independent, lightweight microservices that communicate via secure REST APIs or event-streaming frameworks such as Kafka.
Context engineering applies disciplines that have been practiced for decades in fields such as configuration management, systems engineering, and domain-driven design to LLMs, a new type of system.
Common strategies for mitigating skill bloat include: dividing bounded contexts according to Domain-Driven Design (DDD), introducing a skill registry and metadata annotation, and establishing skill lifecycle management (addition/merging/deprecation).
Practices such as layered architecture, microservices, and domain-driven design are essentially different expressions of the idea of separation of concerns.
Drawing on the concept of ubiquitous language from domain-driven design, Matt created a skill that can scan a codebase, extract terminology, and generate a glossary markdown file.
The work foundation corresponds to the concepts of "ubiquitous language" and "domain model" in Domain-Driven Design (DDD), where the data itself is part of the platform.
DDD（领域驱动设计）由Eric Evans在2003年的著作《Domain-Driven Design: Tackling Complexity in the Heart of Software》中系统提出
BDD draws on the concept of a ubiquitous language from Eric Evans' Domain-Driven Design (DDD), unifying requirements, tests, and documentation through the Given-When-Then three-part structure.
All Facts (10)
Domain-Driven Design (DDD) is a software design methodology proposed by Eric Evans in 2003.
80%UnverifiedDomain-Driven Design (DDD) introduced the concept of 'Ubiquitous Language,' advocating that naming in code should remain consistent with the terminology of the business domain.
60%UnverifiedThe first layer of legacy system refactoring requires systematic decomposition using domain-driven design (DDD), defining clear bounded contexts, and refactoring business domains into independent, lightweight microservices that communicate via secure REST APIs or event-streaming frameworks such as Kafka.
50%UnverifiedContext engineering applies disciplines that have been practiced for decades in fields such as configuration management, systems engineering, and domain-driven design to LLMs, a new type of system.
50%UnverifiedCommon strategies for mitigating skill bloat include: dividing bounded contexts according to Domain-Driven Design (DDD), introducing a skill registry and metadata annotation, and establishing skill lifecycle management (addition/merging/deprecation).
50%UnverifiedPractices such as layered architecture, microservices, and domain-driven design are essentially different expressions of the idea of separation of concerns.
50%UnverifiedDrawing on the concept of ubiquitous language from domain-driven design, Matt created a skill that can scan a codebase, extract terminology, and generate a glossary markdown file.
50%UnverifiedThe work foundation corresponds to the concepts of "ubiquitous language" and "domain model" in Domain-Driven Design (DDD), where the data itself is part of the platform.
50%UnverifiedDDD（领域驱动设计）由Eric Evans在2003年的著作《Domain-Driven Design: Tackling Complexity in the Heart of Software》中系统提出
50%UnverifiedBDD draws on the concept of a ubiquitous language from Eric Evans' Domain-Driven Design (DDD), unifying requirements, tests, and documentation through the Given-When-Then three-part structure.
50%