Clean Architecture with ASP.NET Core 8 | .NET Conf 2023

Clean Architecture (aka Onion, Hexagonal, Ports-and-Adapters) organizes your code in a way that limits its dependencies on infrastructure concerns. This results in much more testable, maintainable code and is ideal for Domain-Driven Design as well as microservices. Learn how to apply it to your ASP.NET Core apps!

Chapters:
00:00 Let's get started
00:06 What is Clean Architecture
01:25 When to use Clean Architecture
03:25 Two approaches to layered architecture
05:57 Demo
07:25 Clean Architecture Rules
08:51 What belongs in the Core project
13:48 Demo
16:23 What about CQRS
16:45 What belongs in teh Use Cases project
17:01 Demo
18:35 What belongs in the Infrastructure project
20:02 Demo
21:29 What belongs in the Web project
22:05 Demo
23:57 The Shared Kernel
24:17 Demo
25:52 Resources
25:57 Q&A

Clean Architecture Template

eShopOnWeb Reference Application

Architect Modern Apps w/ASP.NET Core eBook

More from Steve

#dotnet

[chockshoway]

Great video Steve. Fantastic to see Microsoft finally talking about this, domains and DDD. Hopefully we'll see some domain-centric templates rather than those entrenching anti patterns like focus on the tech choice (MVC) and pushing teams towards procedural code (top level functions).

[kenuahs]

I've read dozens of articles over the years on clean architecture, and a portion of those were tied in to .net apps, and this is by far the best presentation on clean architecture that I have seen! Was especially helpful to see a real-live project as well. Super well done presentation.

[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.

[vishweshhramesh]

Best video to understand CQRS, Clean Architecture without any clutter.

[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 👍

[jan]

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.

[acodersjourney]

Your channel is a treasure trove of knowledge. Thanks!

[mrohailiqbal]

It was a good learning experience through this video. Keep it up.

[FainTMako]

Great presentation. One of my favorites from this year!

[bvboi]

Currently implementing this in my project. Thanks!

[calvinwilson]

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.

[frankhoffy]

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.

[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.

[nwjoxwx]

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 😢)

[Paul-uosv]

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?

[mumk]

great to see Ardalis here, I knew him from his Pluralsight course

[hectorcontreras]

Should I bother seeing the other videos on Clean Architecture with ASP.NET Core 6 (and 7)" before this one, or can I just start here?

[shashankshekhar-clrd]

I need to create project from scratch in dotnet core 8.0 using entity framework..can i refer this folder structure??we will be creating apis

[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