Eric Evans in the book DDD: Tackling Complexity in the Heart of Software presents a model characteristic for Domain Driven Design, which consists of layers: User Interface, Application, Domain and …
Read More
Designing a domain model with as few relationships as possible prevents the code from being complicated and difficult to maintain. On most large systems, relationships between entities cannot be avoided. …
Read More
Many objects do not have their own identity. An example are windows with the same dimensions and the same way of opening and fixing, which do not differ from each …
Read More
Many things are defined by their identity (uniqueness) and not by their attributes. A very good example is a man with features that can change or disappear completely throughout his …
Read More
Bounded context In large applications, there are many models without clearly defined dependencies. As the system develops, the boundaries between models blur and the links between objects become unclear. For …
Read More
The ubiquitous language is used to find an agreement between people who know the technological vocabulary and those who do not use it. Thanks to this, we can create a …
Read More
This post will be the beginning of the description of the DDD approach to designing systems, based on the assumptions of the book Domain-Driven Design: Tackling Complexity in the Heart …
Read More