Clean Architecture Structure

[fretje]

I just ran into this repository:

https://github.com/baratgabor/MyWarehouse

which I think is very nicely done wrt folder/project structure.

Our structure is already getting quite solid (and is very similar to that one), but I think we can still learn a thing or 2 here ;-)

One thing that stands out is that we put a lot of stuff in Infrastructure which should probably stay in the actual Web project (Host in our case). Things like CORS and Versioning and Swagger.

Not saying that needs to be changed immediately. But just something to think about...

[xlogex]

I also noticed something that could be organized differently .... (and in particular the mapping in the application)
But since the Multitenant model I never work ....

[xlogex]

also UnitOfWork could be need?

[fretje]

This discussion is more about the structure... not about features.

But anyway, on the topic of IUnitOfWork (it can be a controversial one): We now switched to the default implementation of the IRepository in Ardalis.Specification, which is working with IAggregateRoot... Everything that goes into one transaction should all be in one AggregateRoot... that's also the reason why the Add, Update and Remove methods on the repository call SaveChanges themselves. So an AggregateRoot is kind of the unitofwork in this case. If you would really want to work with a separate IUnitOfWork, then you would have to have a Repository that doesn't call savechanges.

So it's kind of one or the other, but not both...