Replies: 2 comments 2 replies
-
That's only true because it's in the same project. Once you want to separate one module from the project, for example for scalability reasons MediatR is no longer valid option. |
Beta Was this translation helpful? Give feedback.
1 reply
-
mass transit mediator
…On Sat, Feb 6, 2021, 18:51 Mayo Atte ***@***.***> wrote:
Hey @itinicore <https://github.com/itinicore>, I totally get that.
What I'm hoping to do here is move gradually towards isolated modules. At
the moment I have zero users (still building) and it might be quite a while
(or never) until I have enough users to require isolated modules.
Until then, I would like to be have a simpler implementation while the
modules are together and in memory. This is what spurred my question. How
do i do the simple thing first and the more robust/complex thing later?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#152 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQAM2KXPFQO3ZAEKY4Z6FLS5V6QNANCNFSM4WTAOZPQ>
.
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
oluatte
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to understand the usage of Mediatr vs the custom event bus implementation in the code.
It seems like mediatr could handle both cases in which they are used that is, Mediatr for domain events and the Event Bus for integration events.
Any thoughts on why this done?
Beta Was this translation helpful? Give feedback.
All reactions