.NET 7 💥 - Intro to CQRS and MediatR with ASP.NET Core Web Api
ฝัง
- เผยแพร่เมื่อ 21 ต.ค. 2024
- In this video we will be going to learning about CQRS and MediatR with .NET Web API.
Support me on Patreon to access the source code:
/ mohamadlawand
Base App: • .NET 7 💥 - ASP.NET C...
Let us connect:
🌍 My website - mohamadlawand.com
📸 Instagram - / mohamadlawand087
🐦 Twitter - / moe23
♯ Github - github.com/moh...
🎫 LinkedIn - / mlawand
💥 LinkTree - linktr.ee/moha...
Gear I use (affiliate link): amzn.to/3EbT8Jw
Support my work:
/ mohamadlawand
www.buymeacoff...
Hire Me:
transactions.s...
WHO AM I:
I'm Mohamad, a Enterprise Architect working in Manchester, UK. I make videos about web, cloud, desktop and mobile development.
GET IN TOUCH:
If you’d like to talk, I’d love to hear from you. Tweeting @moe23 directly will be the quickest way to get a response, but if your question is very long, feel free to email me at hello@mohamadlawand.com.
#dotnet #mediatr #cqrs
Amazing In depth and systematic explanation!
The level of detail, structure, and thought you've put into this content is truly remarkable. Fantastic video! Keep up the incredible work!
Straight to the point, simple and well explained! Well done!
Awesome content and detailed explanation for beginners.
Hi, could you please create the notification part also?
this is the only clip where the author actually explains what's happening with the query, the handler and how mediator is using behind the scene the send method to process a query by the handler. Almost all the other videos are just mechanically showing ...this is the query, this is the handler, this is the mediator send ... bla bla bla with zero knowledge transfer. Thank you for the video Mohamad
Super work!
Awesome content! The diagrams really help to understand the high-level concepts. Great job!
simply awesome explanation..
Yes I am also interested in the notifications part
Nice content and project idea end to end.
Awesome content and good explanation. Thank you
wow very nice skills to teaching. Thank you for this valuable content
I love your videos. You explain things in detail, thank you so much. It will be very nice to create the notification path too.🎉🎉👍🤜🤛
Thanks, Mohammad.
love you vids mate, keep it up!
i like your videos like this, thank you.
insightful, thank you
please create notification part as well, thank you.
Excelent content. Congratulations.
This video is perfect
Amazing content
Thanks!
Thank you for your support
With the mediator pattern, are we creating a bottleneck?, by the way the content is good and the explanations is excellent, thanks a lot.
Great video thanks! Is there any particular reason you used suffix 'request' instead of 'command' for the commands?
Well done and informative. Thank you.
Glad it was helpful!
Amazing...
Thank you 😀
Excellent videos. I've scoured this and its previous video to learn CQRS and Mediatr. I can't find how you made Delete and Update async though.
Per usual, soon after I ask for help, I've figure it out. Great videos!!
i use PHP for most of my projects, im new to .NET what is the benefit of using different connection string , does that mean there are multiple database? thanks
Hi, why you do mapping in Handlers and in Controllers?
Awesome
I can't understand for what I need mediatR. So, if I keep all logic in my services, and in the controler's methods I just call methods from my services, why I need to use mediatR? It's easier to avoid mediatR. And also, it requires less code. Can someone explain me, why mediatR is better? Thanks
I wrote an answer to @foonlam7134 , maybe it will help you too.
I have the Exactly Same Question..
There is a lot of English content and I noticed that you are smart, It would be great if your content was in Arabic, or at least had another Arabic content besides the english one.
Thank you.
I'm see a lot if the Mediatr ir cqrs video show only simple crud operations. I have a complex app where i am processing messages that come in deoending on the message type. The method in my current controller has to call several other services and make http requests to third parties as well. My question is do i put all the method logic into the handler or do i need to create a separate command and separate handler for each if the service calls i make. If so, who will be orchestrating the process flow. If we put the whole logic into the handler are we not just moving the logic into another layer? This is where I'm confused. I wish someone would nake a video showing a bit more complexity in the handlers. I understand that they show the simple stuff so that we understand how it works but i need to know what the right approach is for complex logic
I think moving the business logic into its own layer is a benefit for sure, it's a big part of what using mediatR or services or specifications or whatever all have in common. The core business logic lives in one separated later away from all the interactions with the outside world (external APIs, databases, filesystems etc) so your handler/services/specifications are really obvious what their logic is and really easy to test. Whichever of these you pick I'm not convinced make too much difference tbh, as long as you pick atleast one of them!
Hello and thank you for the great content
Can you put all of this in a small project and use the tdd approach
Thank you again
Hello, im try to learning from you. But in this class, i got the '
No service for type 'MediatR.IRequestHandler' has been registred' Error with MediatR. I try to fix this on the internet bu nothing work for me. Do you have any solution for it?
And if you could show how to add a new connection string for the queries
Can you make a video about mediator notifications
yes notification please
Quick question: Does the new connection string improve on performance?
github code is not available it seems
IMO Unitofwork better :)
UnitOfWork does the job just fine but CQRS really makes it easy to scale your API very well and really have a good separation of concerns.
@@blessdarah1256 too much code..
Please explain your videos in Arabic ..... please speak Arabic