Get the latest tech news
Domains listening to many other domains in Event-Driven Architecture
Usually, in an event-driven architecture, events are emitted by one service and listened to by many (1:n). But what if it's the other way around? If one service needs to listen to events from many other services?
Events and Commands with extended criteriaTypeEvent"Tell" - Command"Ask" - CommandDescribes..An event that has happened in the pastAn intention to perform an operation or change a stateAn intention to perform an operation or change a stateExpected ResponseNoneNoneA confirmation that the command has been executed, or an error messageCommunication PatternFire-and-ForgetFire-and-ForgetRequest-ResponseSo in terms of the overall flow, in terms of the structure of communication, “tell” has more in common with events than with an “ask”. But as mentioned above, this requires the notification service to be aware of all sorts of domain events and handle them, and to be extended if more are added. So I’m looking forward to learning more about the readers’ approaches, and to writing further blog posts sharing new insights in the future.
Or read this on Hacker News
