Clean ASP.NET Core API using MediatR and CQRS | Setup

Hello everybody I'm Nick and in this ASP.NET Core tutorial I will show you how you can use CQRS and MediatR to clean up your applications. I will briefly explain what CQRS and the Mediator patterns are and how they apply in our use-case. The I will show you how you can use the MediatR package to decouple your API layer from your application layer, leading to more testable and manageable code.

Don't forget to comment, like and subscribe :)

Social Media:

#aspnetcore #mediatr #cqrs #tutorial

[pratiks]

I don't think I could have gotten such a clear explanation of this pattern anywhere else on the web.
Thanks Nick !

[najibmestaoui]

You can't imagine how happy I am after watching this video! Thank you.

[zokocx]

Great starting tutorial with enough introduction theory, I never used MediatR or even mediator pattern (been stuck at legacy project)
And I really like how MediatR effortlessly made implementing of query and command almost trivial in CQRS pattern.

Keep the excellent videos coming and keep coding.

PS: your videos are worth more than price of coffee to see the source

[jeremi]

I pressed like and subscribed by just watching the first 8 mins of this video, it's one of the best explanations without going full-blown detail yet I understand the main concept! well done!

[ahmedshaker]

Perfect for whom wanna to start and get into MediatR and CQRS, keep up the great work man

[sergiohuanca]

Love your content Nick. I'm just a newbie but learning a lot with your videos! Greetings from Perú!

[MR-neww]

00:00 : Introduction
00:22 : Mediator
02:25 : CQRS
05:27 : Design Overview
06:45 : Coding

[AlejandroVivas]

Video from 2019 and still applies today. This was very well explained. Thank you!

[florin.soldan]

Really good explanation and the demo was great, not too much not too less, really good balance. Thanks!

[triggerhappy]

Great video! Maybe because I setup my project almost identitcal. I'm loving how the code is so organized and clean!

[adrenalinea]

best video regarding MediatR and CQRS I could find! Thanks a lot!

[mohamedelbasmy]

I really enjoy watching your videos, very interesting tops and very clear explanation, Thanks you so much for all your efforts.
we wait all your newly tutorials.

[ilovepandaypoe]

really really great tutorial. I was able to follow along and everything working as expected. wow!

[ben.thornhill]

Awesome content! You are a great teacher. Keep up the great work. I subscribed and look forward to more videos.

[ajagbequadri]

this is one of the best tutorials on CQRS.

[MrRozekkk]

Thanks for that tutorial. Very clearly described what to use and how. I've liked that CQRS pattern :D You deserve sub and like :)

[mmsky]

Great tutorial, awesome explanation. Thank you so much for providing the source code.

[CollegeCode]

Excellent video Nick! Keep up the great work.

[edelwater]

In general this is partly the evolution from a generic service response model to send from services to controllers. I noticed that in some cases when a controller returns multiple http statuses and messages depending on conditions there is an overlap in what you want to return from the service and the return value from the controller. The generic service response model then gets a kind of mapping which makes it confusing. So e.g. if the controller returns status xx1, xx2, xxx3, xxx4, xx5 depending on conditions with different (translated) messages when are only known in the service layer in terms of "content" for the message, there needs to be a mapping somewhere between what the service returns and the controller returns. So in the end the generic model returns a model with e.g. enums or something alike but then the mapping to what http status and which translated message then gets returned (which is more difficult if they are dynamic so not a lookup) is in terms of placement still dependent on what gets being send. (for everything that is generic its easy because you could handle that in a filter or middleware)

[maidamsanthosh]

What an explanation, easily understood. Thanks for the video..