Contents
How are domain entities used in domain modeling?
Entities are pretty much the bread and butter of domain modeling. These are some of the primary trait of entities. Entities should be the first place that we think of to put domain logic.
Where to place business logic in Domain Driven Design?
Entities are the first natural place we should aim to place business logic in domain-driven applications. In this article, we talk about the roles and lifecycle of an entity in Domain-Driven Design. This is part of the Domain-Driven Design w/ TypeScript & Node.js course.
What is the role of entities in DDD?
The role of entities in DDD. Entities are pretty much the bread and butter of domain modeling. These are some of the primary trait of entities. First place to put business logic (if it makes sense) Entities should be the first place that we think of to put domain logic. When we want to express what a particular model: can do; when it can do it
When does an entity make sense to exist?
An entity only makes sense to exist if it has a particular type to it like Car extends Entity . The id for this class is readonly. So it shouldn’t be able to be changed once instantiated. Also a pretty logical design decision if you ask me.
Is the validation logic delegated to value objects?
Validation logic on object creation is normally delegated to Value Objects, but what can happen (and when) is up to the entity. One of the earliest mistakes I was making in domain modeling was exposing getters and setters for everything. So let’s be explicit about the fact that that’s not the best thing to do.
How are domain services and application services related?
As we discussed in a previous post, domain logic is everything that is related to business decisions. Domain services, therefore, participate in the decision-making process the same way entities and value objects do. And application services orchestrate those decisions the same way they orchestrate decisions made by entities and value objects.
Can a domain entity hold an invariant for US?
The domain entity doesn’t hold this invariant for us. And it’s impossible to introduce such an invariant without violating the entity’s isolation because in order to check this precondition it will have to call the 3rd party service. So, what to do in such situation?
When do domain entities have to be valid?
Domain entities should always be valid entities. There are a certain number of invariants for an object that should always be true. For example, an order item object always has to have a quantity that must be a positive integer, plus an article name and price.
Can a domain model be kept lean with exceptions?
However, from a DDD point of view, the domain model is best kept lean with the use of exceptions in your entity’s behavior methods, or by implementing the Specification and Notification patterns to enforce validation rules.