CleanArchitecture VS eShopOnWeb

Looking at this, it has similar aspects as ASP.NET Core, and the same flaws as the Controller per class design used. Methods such as "create", "show" and "store" do not share a state, they shouldn't share a class either.

However, you can rectify this, by just not trying to share a class with any of those. In .NET Steve Smith, aka Ardalis shows how to do this with his Clean architecture idea [1], Idea is to make a class for each endpoint. This also makes it easier for "Update" classes to share functionality with other "Update" classes and so on.

[1]: https://github.com/ardalis/CleanArchitecture/tree/main/sampl...

🔴 [CleanArchitecture] (Learning Template + Docs): A starting point for Clean Architecture with ASP.NET Core. Clean Architecture is just the latest in a series of names for the same loosely-coupled, dependency-inverted architecture.

Here’s a few: - complex domain driven example using vertical slice - another DDD example - clean architecture template by Jason taylor - clean architecture template by ardalis

This repository is a good place to start with modern c# code, specifically ASP.NET

https://github.com/ardalis/CleanArchitecture

If you want to try clean architecture, you can check out Steve smith’s repo or Jason Taylor’s repo.

🔗 Clean Architecture repository | GitHub

- https://github.com/dotnet-architecture/eShopOnWeb (a Microsoft example -- also includes the link to a recent livestream which provides an overview)

https://github.com/dotnet-architecture/eShopOnWeb for studying best practices

dotnet-architecture/eShopOnWeb: Sample ASP.NET Core 7.0 reference application, powered by Microsoft, demonstrating a layered application architecture with monolithic deployment model. Download the eBook PDF from docs folder. (github.com)

There is also https://github.com/dotnet-architecture/eShopOnWeb

A fully featured sample ASP .NET Core Application