Clean architecture with ASP.NET Core
summary
Shows a concrete ASP.NET Core repo layout (three projects: ApplicationCore, Infrastructure, Web) taken from eShop OnWeb and demonstrates flipping dependencies so the core has no framework or DB ties while infrastructure implements interfaces and is wired at startup. Uses mediator for command/handler flow to keep controllers thin and a monkey framework to mock an IAsyncRepository in unit tests for BasketService. Demo runs (Visual Studio hiccups but features work) and unit tests exercise core logic.
AI-written summary · about
chapters (22)
- 0:00Start
- 4:36ASP.NET Core brings a lot to the table
- 6:40Building applications with ASP.NET Core
- 12:43Goals of the architecture
- 15:26Single responsibility
- 17:03Dependency inversion
- 18:43Explicit dependencies
- 20:11Persistence ignorance
- 21:49Bounded context
- 23:56From one application to clean architecture
- 25:31Typical all-in-one application
- 27:07Moving to layers
- 28:31A typical layered architecture
- 29:05Disadvantages of plain layering
- 29:50A layered ASP.NET Core project
- 30:04Scaling into the cloud
- 30:37Deploying and scaling this type of applications
- 32:17Finally, clean architecture
- 34:37Clean architecture diagram
- 38:59Who goes where?
- 47:10What about the controller actions?
- 55:44Summary
related talks
59mClean Architecture With ASP.NET Core
01h 01mAn Opinionated Approach to Using ASP.NET Core
57mAn Opinionated Approach to ASP.NET Core
56mAn Opinionated Approach to ASP.NET Core
59mAn Opinionated Approach to ASP.NET Core
56mAn Opinionated Approach to ASP.NET Core
01h 02mPatterns for application development with ASP.NET Core
41mFull Stack .Net Architecture