Hi William, thanks for this great question and feedback!

When I created this library some years ago (2017), MediatR was already available and it provided a very generic implementation of the mediator pattern.

It was great, but I always needed to create my own command, queries, event interfaces and other wrappers to ensure the development teams were using it properly. It also had some limitations with the pipeline for me because, since it was also very generic, it was difficult to add specific behavior just to commands or queries without having to use some type of reflection or being dependent from the DI container capabilities, so I decided back then to create a more specialized library to help implement CQRS+ES patterns.

I haven't used MediatR since 2017, but just from what I'm seeing in the source code I still can't differentiate from a command or query without creating my own interfaces.

For me, who likes everything strong typed and more strict, that is a limitation in the contracts I can't live with.

But at the end of the day, both libraries should bring you similar results.