#mediatr — Public Fediverse posts

Requestum 1.2.5: теги, политики устойчивости и встроенное логирование

Привет, Хабр! Около месяца назад я рассказывал о Requestum — CQRS-библиотеке для .NET, созданной как бесплатная альтернатива MediatR. После той публикации в комментариях многие справедливо спрашивали: «Зачем нужна ещё одна CQRS-библиотека? Есть же Mediator, Wolverine, Brighter и другие проверенные решения. Чем твоя альтернатива лучше?» Честный ответ на тот момент был: «Пока, наверное, ничем особенным — разве что MIT лицензией и чуть лучшей производительностью» . Но за этот месяц я постарался это исправить. Этот пост — мой ответ на те вопросы и рассказ о фичах, которые делают Requestum достойным внимания, а не просто «ещё одной библиотекой в списке».

https://habr.com/ru/articles/974616/

#net #cqrs #open_source #mediatr #c# #requestum #архитектура_по

AutoMapper and MediatR Commercial Editions Launch Today | by Jimmy Bogard.

https://www.jimmybogard.com/automapper-and-mediatr-commercial-editions-launch-today/

#dotnet #csharp #automapper #mediatr

🎙️ Bonus #BeerDrivenDevs is out now!

#MassTransit and #MediatR going commercial on the same day felt like a tipping point.

We couldn’t wait 2 weeks to unpack it.

Is the .NET ecosystem in crisis?

Cheers!🍻

🌐 https://dub.sh/Yn8SDvq
🍎 https://apple.co/4iTVBuG
🟢 https://spti.fi/BVUCRYf

#dotnet #OpenSource #DeveloperCommunity #OSS

@maxitb @jonsagara another #opensource #dotnet project bites the dust. I get it that #opensourced projects where must be funded and sustainable somehow, but that's a terrible news. #fluentassertions and now #mediatr and #automapper 😔 that's just terrible.
Companies should pay for it, not developers!!!

@maxitb @jonsagara another #opensource #dotnet project bites the dust. I get it that #opensourced projects where must be funded and sustainable somehow, but that's a terrible news. #fluentassertions and now #mediatr and #automapper 😔 that's just terrible.
Companies should pay for it, not developers!!!

Lightweight In-Memory Message Bus Using .NET Channels by Milan Jovanović.

#dotnet #csharp #messagebus #mediatr #patterns
https://www.milanjovanovic.tech/blog/lightweight-in-memory-message-bus-using-dotnet-channels

I was at a brilliant #ConFoo talk and realized #MediatR is the #Redux / #Flux pattern for server-side #ASPnet. https://github.com/jbogard/MediatR Great talk https://in.linkedin.com/in/davideguida.

A thread about #cleanarchitecture, #vsa, #mediatr, #cslanet and #softwarearchitecture

https://fosstodon.org/@rockylhotka/111925831104217117

This was a timely interview, as someone recently started a thread in the #cslanet forum about #CleanArchitecture, #MediatR, and #VSA

All of these things have come into being during the lifetime of #cslanet (27+ years is a long time), and it is interesting to do a compare/contrast with these "newcomer" ideas😁

Being a long-time advocate of object-oriented design around user scenarios (use cases), the idea of vertical slices for functionality makes a lot of sense to me.

1/🧵

Authored my first blog post 🎉

It's about domain-event dispatching using an outbox pattern with EF and MediatR.

Any feedback good or critical would be greatly appreciated 🙏

#dotnet #domaindrivendesign #ddd #mediatr #entityframework

https://themagnificent11.github.io/themagnificent11/#domain-event-dispatching-using-the-outbox-pattern-with-entity-framework

Source-generated Mediator that honours Mediatr's interfaces #dotnet #mediatr

https://youtube.com/watch?v=aaFLtcf8cO4&si=MVjKySPpxV0HQYas

Without #MediatR, plain OOP patterns to get the same functionalities idiomatically.

https://arialdomartini.github.io/without-mediatr

#csharp

I keep hearing about frameworks like Brighter/Darker, Wolverine ("critter stack") etc that are alternatives to Mediatr.

Any suggestions on what is better from a DDD or event-driven development point of view taking into account developer productivity and performance?

#dotnet #ddd #evetdrivendevekopment #mediatr #brighter #wolverine

I keep hearing about frameworks like Brighter/Darker, Wolverine ("critter stack") etc that are alternatives to Mediatr.

Any suggestions on what is better from a DDD or event-driven development point of view taking into account developer productivity and performance?

#dotnet #ddd #evetdrivendevekopment #mediatr #brighter #wolverine

I keep hearing about frameworks like Brighter/Darker, Wolverine ("critter stack") etc that are alternatives to Mediatr.

Any suggestions on what is better from a DDD or event-driven development point of view taking into account developer productivity and performance?

#dotnet #ddd #evetdrivendevekopment #mediatr #brighter #wolverine

I keep hearing about frameworks like Brighter/Darker, Wolverine ("critter stack") etc that are alternatives to Mediatr.

Any suggestions on what is better from a DDD or event-driven development point of view taking into account developer productivity and performance?

#dotnet #ddd #evetdrivendevekopment #mediatr #brighter #wolverine

I keep hearing about frameworks like Brighter/Darker, Wolverine ("critter stack") etc that are alternatives to Mediatr.

Any suggestions on what is better from a DDD or event-driven development point of view taking into account developer productivity and performance?

#dotnet #ddd #evetdrivendevekopment #mediatr #brighter #wolverine

The number of posts confusing #CQRS with #CQS is astonishing.

Just like the number of articles stating that #MediatR is an implementation of the GOF Mediator. Some even link the book: if they only followed the link they would easily realize GOF Mediator is a completely different pattern.

The number of posts confusing #CQRS with #CQS is astonishing.

Just like the number of articles stating that #MediatR is an implementation of the GOF Mediator. Some even link the book: if they only followed the link they would easily realize GOF Mediator is a completely different pattern.

The number of posts confusing #CQRS with #CQS is astonishing.

Just like the number of articles stating that #MediatR is an implementation of the GOF Mediator. Some even link the book: if they only followed the link they would easily realize GOF Mediator is a completely different pattern.

The number of posts confusing #CQRS with #CQS is astonishing.

Just like the number of articles stating that #MediatR is an implementation of the GOF Mediator. Some even link the book: if they only followed the link they would easily realize GOF Mediator is a completely different pattern.

The number of posts confusing #CQRS with #CQS is astonishing.

Just like the number of articles stating that #MediatR is an implementation of the GOF Mediator. Some even link the book: if they only followed the link they would easily realize GOF Mediator is a completely different pattern.

If you're migrating #MediatR v12, read the migration guide super carefully!

If you use behaviors and previously added the `TRequest : IRequest<TResponse>` generic constraint when moving to v11, you need to revert that back to just `notnull` otherwise requests with only the non-generic `IRequest` will SILENTLY no longer be processed by it; no compilation or runtime errors. I now doubly appreciate my API acceptance tests, otherwise I wouldn't have spotted it!

https://github.com/jbogard/MediatR/wiki/Migration-Guide-11.x-to-12.0

#dotnet

Trying the “strangler fig” approach to an old webforms 4.8 site and am using #dotnet 7.0 #efcore with postgres (first time!) for identity but now comes the “how to I handle user data requests from the old site”. Thought about an API but before I did - anyone know if there is a way to send #Mediatr request from a 4.8 app and let it be handled in a net 7.0 library? Can’t reference it directly in the 4.8 app but I imagine there’s a way..

Anyone have advice on whether it's better to to use classes or records for MediatR INotifications/IRequests?

#Mediatr #Mediator

@BearNuzzler

I saw a microservice that has 1 api endpoint on a controller, and 1 service that does the work. And between them: #mediatR.

WTF. There was no benefit whatsoever to interposing mediatR there. None.
Use it when it makes sense, not by rote.

Currently learning more about Clean Architecture.
Using MediatR seems to be quite en vogue these days. But I don't really understand why. There are some benefits to this abstraction but the code obfuscation and the Service Locator pattern through the backdoor it brings seem like a really bad design decision. It totally removes the dependency declaration of a class which seems horrible to test.
Or am I just missing something here?

#csharp #dotnet #CleanArchitechture #MediatR