An event is something that has happened in the past. A domain event is, something that happened in the domain that you want other parts of the same domain (in-process) to be aware of. The notified parts usually react somehow to the events. Domain events: design and implementation Benefits Since domain events are… well, events, it comes with all the benefits and use cases that you would have if you implement some sort of event driven architecture: Reduce coupling between the effect and the consequence: creating a user and notifying that a user was created have different levels of complexity, different responsibilities, different reasons to change… You won’t have a… Read More
Continue Reading
The brand new black box in the shop
Before starting turning things upside down, I owe you an apology: in this article I’m not going to talk about architecture with a big picture, I will do it with a simple one. Do not take this as an architecture article. Real-life background In human history (well, I would extend this to animal history), every time we all needed to do something, we tried to do it as a group. If we needed to do actions in the town, we as groups (not as individuals) decided what to do. If you are planning to build a house, you probably sign a contractor firm that will know what to do and… Read More
Continue Reading