MWaseemZakir's platform  covers topics related to software development, technology trends, and coding tutorials. Through articles, tutorials, and personal anecdotes, MWaseemZakir offers insights into programming languages, development frameworks, and best practices in software engineering. Readers can learn about software design principles, development methodologies, and emerging technologies to enhance their coding skills and build high-quality software applications.

Waseem .NET Newsletter

With MediatR going commercial, developers are exploring alternatives. Wolverine, a free NuGet package, offers next-generation .NET mediator and message bus capabilities. Using Wolverine involves simple naming conventions and no special interfaces, making it a streamlined choice for handling messages in .NET applications. It includes features like fluent validation and can be configured to use only core mediator services to keep applications lean and efficient.

Wolverine as Mediator in .NET

Looks promising. How solid is the community behind it?

I really like the fact that this package is “simple” and straightforward, also the “cascading” commands feature looks like it could resolve a lot of problems developers could have when doing Event Driven with MediatR (such as not having particular orders when firing multiples events when the entities are updated).
However, what I don’t like about it is the fact that it resolves the handlers automatically.
If I were to use it, I would probably create an interface that dictates the handlers structures (for centralized log/event managements ease of use) but I would have liked to have the choice when configuring this package to choose between a “smart resolver” or a more traditional way of doing it. Though as the package is open-source I’ll look through the issues and maybe issue a PR for it.
Also, I haven’t seen a way to pass a CancellationToken to the methods, that could be problematic.
Anyway, thanks for the sharing 🙏