CQRS & MediatR in a .NET 8 Web API 🚀

  Рет қаралды 9,952

Patrick God

Patrick God

Күн бұрын

Пікірлер: 20
@codefoxtrot
@codefoxtrot 3 ай бұрын
It was wayyyy simpler before MediatR and CRQS, but thanks for explaining in a quick demo! Though it leaves me wondering what's the benefit of doing this in a larger project? Seems like it just adds another layer of work.
@SireTheKing
@SireTheKing Ай бұрын
CQRS is a pattern that allows developers to decouple everything, which makes it easier to update and feature add-ons via interfaces. it also allows for easier testing since you can mock the dependencies. This creates loosely coupled applications, and the trade-off is more complexity.
@-INC0GNIT0-
@-INC0GNIT0- 3 ай бұрын
Great stuff, I always like your channel because you always show stuff we developers really need and the common streamers always seem to ignore to show like: authorization, mailing, refreshing tokens, ... it's always very knowledgeable engineering concepts
@adam-xt8te
@adam-xt8te 3 ай бұрын
God created The World in 7 days. Patrick explaned CQRS in 22 minutes.
@PatrickGod
@PatrickGod 3 ай бұрын
😂
@harishchaudhari9681
@harishchaudhari9681 Ай бұрын
True fabulous tutorial on CQRS❤❤❤❤
@dasfahrer8187
@dasfahrer8187 3 ай бұрын
Interesting, but it's just another abstraction layer that doesn't buy you much. If you're managing multiple brownfield projects that already have a standard pattern, introducing this only adds time and confusion to technical debt as you're now having to navigate multiple ways of doing things.
@PatrickGod
@PatrickGod 3 ай бұрын
Thanks for sharing your thoughts! What approach do you prefer for implementing the same feature without adding an extra abstraction layer?
@dasfahrer8187
@dasfahrer8187 3 ай бұрын
@@PatrickGod Well, for some context, we have dozens of projects with API interfaces in them that hit various services across our own internal network as well as external endpoints. That in and of itself is a lot to manage so we try to keep things as generic as possible w/o having to rely on too many third party NuGet packages that don't bring much to the table for us. Because of that, we rolled our own base service implementations and interfaces to fit our security and network requirements. They don't follow a specific design or organizational patterns other than separating concerns and decoupling key areas where we know potentially breaking changes have taken place in the past or are likely to take place. We do regularly re-evaluate our architecture and implementations to see if there are any new ideas/tech that may help us manage things more efficiently, but so far we have yet to find anything significant enough to warrant a complete redesign and rebuild. Typically what we'll do is change something like a series of classes over to records and make the corresponding downstream changes to properly utilize them.
@eyoo369
@eyoo369 2 ай бұрын
Everyone saying that Mediatr is useless. For our team the biggest advantage is having controllers with literally 1 line of code and a single dependancy injection which is MediatR itself. Also having your project structured by Features (commands & queries) makes it so much more easy to navigate as opposed to a God-like 1000+ line service class. And the best of all is that testing commands & queries is a lot easier than testing and mocking a service class. Everyone can work on a feature and saves us git merge headaches when 2 or more devs are working in the same Service class.
@qubitza
@qubitza 3 ай бұрын
Thanks for the Video and the super explanation ❤ It might feel super clean in the first place. However, for me the mediator added another layer of abstraction which made it harder to analyze dependencies. Moreover, I wondered how to execute multiple commands in a transaction.
@daWoody01
@daWoody01 3 ай бұрын
Any benefits or issues using MediatR in a Blazor component? I usually inject a service into a Blazor component and use the service to make any queries or commands.
@imadabab
@imadabab 2 ай бұрын
Great video. Thanks a lot. Very clear.
@TheLUCKYONETutorials
@TheLUCKYONETutorials 3 ай бұрын
I get the idea. But it seems just like another layer of work and complexity. I dont think that I want to implement this every time I start a new project..
@dimasvyrydiuk5955
@dimasvyrydiuk5955 Ай бұрын
Thanks, you taught me how to work with the backend. Best)
@samehgenah8067
@samehgenah8067 3 ай бұрын
You always different👍
@n.sharma5810
@n.sharma5810 Ай бұрын
Hi Patrick, can we implement repository in this example?
@wordlifejohn1122
@wordlifejohn1122 Ай бұрын
You the 🐐
@portahack
@portahack Ай бұрын
Amazing video, really good example and very well explained
@quanghungnguyen3018
@quanghungnguyen3018 3 ай бұрын
thanks a lot 😀
Как реализовать сервис с CQRS | Mediator
16:40
Fix Your Controllers By Refactoring To Minimal APIs
14:56
Milan Jovanović
Рет қаралды 40 М.
Officer Rabbit is so bad. He made Luffy deaf. #funny #supersiblings #comedy
00:18
Funny superhero siblings
Рет қаралды 3,2 МЛН
From Small To Giant Pop Corn #katebrush #funny #shorts
00:17
Kate Brush
Рет қаралды 69 МЛН
Don't Use Polly in .NET Directly. Use this instead!
14:58
Nick Chapsas
Рет қаралды 63 М.
.NET and C# are in trouble. Here is what I'd do.
10:57
Ed Andersen
Рет қаралды 71 М.
The Free Way to Create Awesome PDFs in .NET
12:45
Nick Chapsas
Рет қаралды 46 М.
Stop Using FirstOrDefault in .NET! | Code Cop #021
12:54
Nick Chapsas
Рет қаралды 71 М.
How principled coders outperform the competition
11:11
Coderized
Рет қаралды 1,7 МЛН
Being Competent With Coding Is More Fun
11:13
TheVimeagen
Рет қаралды 78 М.
Brutally honest advice for new .NET Web Developers
7:19
Ed Andersen
Рет қаралды 196 М.
Officer Rabbit is so bad. He made Luffy deaf. #funny #supersiblings #comedy
00:18
Funny superhero siblings
Рет қаралды 3,2 МЛН