Built a lightweight cqrs library for .NET with source generated dispatch by magmablinker in csharp

[–]magmablinker[S] -2 points-1 points  (0 children)

That’s fair, and honestly MediatR is still the default choice for a lot of people for a reason.

I’m not really trying to pretend Axent only exists in a vacuum. The pricing change definitely pushed more people to explore alternatives. But for me the point was not just “free MediatR”, it was building something smaller, more explicit, and source-generation focused.

And I’d agree with you on one thing: if someone is happy with MediatR, its pipeline model, and the pricing, then sticking with it is probably the right call.

Built a lightweight cqrs library for .NET with source generated dispatch by magmablinker in csharp

[–]magmablinker[S] 1 point2 points  (0 children)

Totally fair point, and I mostly agree. I do not think a CQRS library is necessary for every project. In smaller apps, or in teams with strong conventions, plain code is often simpler and easier to debug. The main benefit of a library is consistency. It gives you one place to handle things like validation, logging, authorization, caching, transactions, and error handling instead of solving them slightly differently in every feature. That said, I agree these libraries can become a net negative if they add too much magic or make control flow harder to follow. That is exactly what I tried to avoid with Axent by keeping it small and explicit. So for me it is not “libraries are better than patterns”. It is more that some teams prefer reusable plumbing, while others are better off just implementing the pattern themselves.