CleanArchitecture VS MediatR

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

MediatR – GitHub

MediatR GitHub Repository

MediatR: https://github.com/jbogard/MediatR

MediatR simplifies in-process messaging, CQRS, and domain events.

We need something to do the work of calling the tag repository and mapping to our dto. This will be a class known as a handler. The Web UI will pass a request - encapsulated as an object - to an instance of this handler. The handler will talk to the repository, map the result to a dto, and then return a response. We could (quite easily) write the code for all this ourselves. However there is an elegant library called MediatR that does this job already. Lets use it.

You probably noticed that .SetName() returns a Either. You may have come across Unit in libraries like MediatR or Language-Ext. It's a simple construct representing a type with only one possible value. We use it as a placeholder for operations that do not return a value but may return another state. In our example, .SetName() is a Command that does not return a value but may fail. Therefore, the monad Either carries two possible states: Right (without value) or Left (with an Error).

The widely used MediatR library[0] could be used to do that as well, just FYI.

[0]: https://github.com/jbogard/MediatR