Tag: Domain Model
All the articles with the tag "Domain Model".
-
[DDD Intro #11] Value Object: Expressing domain concepts instead of primitive values
When thinking of DDD's tactical patterns, many people start with Entity. Objects with identifiers, lifecycles, and state changes are certainly important. But in real code, the smallest and clearest starting point for revealing domain meaning is often a Value Object.
-
[DDD Intro #4] Bounded Context: A model is consistent only within a boundary
If asked to choose just one of the most important concepts in DDD, many people would say Bounded Context. At the same time, it is also one of the most misunderstood concepts.
-
[DDD Intro #3] Ubiquitous Language: Good design starts with good language
Ubiquitous Language is one of the most important concepts in DDD, and also one of the easiest to treat lightly. Many teams understand Ubiquitous Language as little more than "creating a glossary." Of course, organizing terms is a good start. But Ubiquitous Language is much deeper than a glossary.
-
[DDD Intro #2] A model is not a copy of reality
To understand DDD, we first need to rethink the word "model." Many people think of a model as something that copies reality as accurately as possible. There is a member in reality, so we create Member. There is an order, so we create Order. There is a payment, so we create Payment. We try to include every attribute that exists in reality.