Is it true that domain events must be handled in the same process? According to .NET Microservices: Architecture for Containerized .NET Applications that’s the way things are. This rather radical statement raises some doubts.
Let’s do some investigations in this area.
What is a domain event according to DDD experts:
- Eric Evans: “Something happened that domain experts care about” src.
- Vaughn Vernon: “Domain Events will help you … to share what has occurred within your model with the systems”.
But. Martin Fowler: “The essence of a Domain Event is that you use it to capture things that can trigger a change to the state of the application” src. Hmm, not quite what we saw above. But taking into account the notes that “this material is in a very draft form,” we can exclude this definition from consideration.
Also, we have one more opinion from code opinion that “Generally, Domain Events will be referred to as “Inside Events” because they don’t leave their boundary” and this does not mean that all this must be handled in-process.
So, why only in-process?