CleanArchitecture VS Mapster

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

Overall i now use a DDD style approach with Mediatr based on https://github.com/ardalis/CleanArchitecture/tree/main/src as well as snippets from Microsofts https://github.com/dotnet-architecture/eShopOnWeb

🔴 [Mapster] A fast, fun and stimulating object to object Mapper! Mapster was designed to be efficient on both speed and memory. You could gain a 4x performance improvement whilst using only 1/3 of memory.

Mapster

Have you read this part in their documentation? https://github.com/MapsterMapper/Mapster/wiki/Data-types

Which is the main reason I don't use it anymore. I can still stand behind why it was created and what it was trying to solve. If you still want to use a mapper I would recommend Mapster as it supports source generation so you can see all code and it's references.

Gotta add a shoutout to Mapster which does pretty much the same thing also using source generation.

I highly recommend Mapster (https://github.com/MapsterMapper/Mapster)

We use Mapster coupled with FastExpressionCompiler and have been very happy with it.

Try Mapster

I hope I managed to convince you and proved the value of unit tests for mappings, so let's move on to the next example. We're going to use AutoMapper, but from a testing standpoint, the choice of mapper makes no difference. For instance, we can replace AutoMapper with Mapster and it won't affect our tests in any way. Moreover, the existing tests will indicate whether our mapping refactoring was successful or not, which is one of the points of having unit tests 🙂