@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.
@vishweshhramesh2163
Best video to understand CQRS, Clean Architecture without any clutter.
@जयमहाराष्ट्र24
Great, Thank you Steve. I am .NET dev but not into web development. But I could follow easily. Its clean.
@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.
@bvboi
Currently implementing this in my project. Thanks!
@mrohailiqbal
It was a good learning experience through this video. Keep it up.
@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.
@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.
@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.
@Paul-uo9sv
This is the best video yet on clean architecture
@sdudnic
how should we link the client project here, like Angular application? I suppose a folder like Client to add to the Web solution?
@IncFromThePen
Thank You loads of success!!
@acodersjourney
Your channel is a treasure trove of knowledge. Thanks!
@martinaaron7304
Really great video. Learned a lot.
@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 😢)
@mumk
great to see Ardalis here, I knew him from his Pluralsight course
@mattdoa2
16:01 - Isn't it true that you might never easily understand what has subscribed to your event? (So by changing the event name or removing it, you could cause a lot of issues with event handlers). I'm imagining this becoming a source of technical debt (in terms of complexity to maintain and complexity to clean up).
@FainTMako
Great presentation. One of my favorites from this year!
@jacobstamm
By using raw SQL queries instead of starting with an entity and doing a .Select() from that, it’s worth noting that using the EF InMemory data provider isn’t going to be enough for your unit tests
@chockshoway