Introduce IMessageBus unifying interface for Commands+Events #5
Labels
enhancement
New feature or request
Comments
kzu
added a commit
that referenced
this issue
Jul 25, 2022
The new interface unifies access to both patterns, Commands and Events, so that consumers can take just one dependency. Fixes #5
kzu
added a commit
that referenced
this issue
Jul 25, 2022
The new interface unifies access to both patterns, Commands and Events, so that consumers can take just one dependency. Fixes #5
kzu
added a commit
that referenced
this issue
Jul 25, 2022
The new interface unifies access to both patterns, Commands and Events, so that consumers can take just one dependency. Fixes #5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's quite common for consumers of Merq to provide command handlers that in turn can execute other commands or publish events. So in practice, consumers end up having a dependency on two interfaces whenever this happens.
The combination of both patterns in a single new interface would simplify this scenario, and subsumes both ICommandBus and IEventStream.
The new interface would provide all members of ICommandBus, and for the IEventStream, we'll change the naming to
IMessageBus.Observe<TEvent>andIMessageBus.Notify<TEvent>, which are more idiomatic than the existingOf<TEvent>andPush<TEvent>, which wouldn't be quite self-explanatory in the combined interface.The text was updated successfully, but these errors were encountered: