'Entity' base class with 'DomainEvents'
I have seen many people using the 'Entity' base class for EFC models with 'DomainEvents'. I wanted to know its purpose and, in general, what it does.
2 Replies
So I think overall the aim is to use domain events to propagage behavior between multiple entities
When it comes to why they would just place them in a list, that's a good question to be honest
I could imagine the goal is to have multiple events in the scope of a transaction without immediately forwarding them to e.g. a database transaction to allow tests to just grab the List<T> (and also to make sure the events are applied in the scope of a domain "transaction", not just rolling to the database in the middle of it)
And then applying all the events prior to writing it to the database
So what i found it is, when an event is triggered in an entity, it is stored in a list of domain events. Before saving changes to the database, these events are collected. After the transaction is successfully committed, the events are dispatched, usually via an event bus or mediator. Basically like you said.