Domains listening to many other domains in Event-Driven Architecture
reactivesystems.eu
Domains listening to many other domains in Event-Driven Architecture
1–5 of 5 posts
Re: Domains listening to many other domains in Event-Driven Architecture
#2[flagged]
Re: Domains listening to many other domains in Event-Driven Architecture
#3[flagged]
[deleted]
Re: Domains listening to many other domains in Event-Driven Architecture
#4[deleted]
Re: Domains listening to many other domains in Event-Driven Architecture
#5Interesting way of looking at it. The way I’ve usually seen it is by modeling events more like “classes” where an event has a “type” and can inherit other “types” or “interfaces”. So if you want a notification to go out with a domain event, it must implement the “notify” interface.
Commands don’t belong on an event bus though, IMHO. Commands are method calls (or RPC) not messages.