@जयमहाराष्ट्र24
Great, Thank you Steve. I am .NET dev but not into web development. But I could follow easily. Its clean.
@Jason_Shave
Love this topic. I can tell you’re rushing through some of this content though due to the short session time constraints. Would be great to have more time on these topics and the same goes for most of the other content too.
@ricardos3756
To the person who asked about CQRS vs Specifications. I believe you may be looking at it as if linq was only used with data coming from the database. As you know they can work together, and they do most of the time, but let's not forget that Linq is also useful with many other object types, not just data, and I believe it is in those scenarios, where you may find yourself applying the same Linq code multiple times, and this is where you will benefit from having Specifications.
@vishweshhramesh2163
Best video to understand CQRS, Clean Architecture without any clutter.
@jan5310
Just want to say thank you for your very good explained clean architecture presentation! Hopefully you can extend this presentation in a more indepth series. I am sure to be checking out your template and play with it.
@calvinwilson3617
Love your template, I would argue that the biggest advantage of Clean Architecture aside from the dependency enforcements as you mentioned, is that you can easily swap out and configure the entire infrastructure layer. This can be extremely useful when you will have multiple clients/front ends. You can reuse the entire business logic and only create different implementations for the infrastructure layer. Most useful IMO for hosted Blazor WASM solutions although blazor itself still has a bit to go and can be frustrating to debug.
@fboucheros
Amazing talk! Love it! Architecture is not an easy topic and you made it clear and approachable. I'll do a "donet new" to continue my exploration.
@Paul-uo9sv
This is the best video yet on clean architecture
@mrohailiqbal
It was a good learning experience through this video. Keep it up.
@bvboi
Currently implementing this in my project. Thanks!
@HiepDuong-q8f
thanks for amazing presentation. Our team have ~10 micro-services on production with clean architecture.. and I personally don't recommend it.. The benefits of Clean Architecture are true, but not as big as we talk (for most case). However the downside of Clean Architecture are Bigger than we think.. Unfortunately not many peoples share the bad sides of Clean Architecture... My recommendation is Vertical Architecture. (If we could rewrite all our microservices again 😢)
@acodersjourney
Your channel is a treasure trove of knowledge. Thanks!
@martinaaron7304
Really great video. Learned a lot.
@IncFromThePen
Thank You loads of success!!
@bmassioui
Thanks, Ardalis for this amazing presentation, which made the CA very simple and easy to comprehend. From my own perspective, I'd like to see those NuGet packages' code-base in the project, which will give them full control over them to maintain and adapt them based on the needs 👍
@FockewulfAz
Fantastic! God bless you!
@mumk
great to see Ardalis here, I knew him from his Pluralsight course
@american_coder
Great presentation Steve. Our agency had implemented something very similar in the past where we inverted the dependency between the business layer and the data access layer, so this seems like a logical progression for us. We're currently debating the virtues of a BFF layer too. I'm wondering if that will somehow factor into clean architecture in the future. The logic to combine data from multiple APIs needs to go somewhere after all.
@FainTMako
Great presentation. One of my favorites from this year!
@chockshoway