Architectural advice needed
Hi, as the title suggest I am looking for advice on my current architecture and how I can improve things. I have some knowlegde on both onion architecture and clean architecture.
My current solution is setup like this:
In brief, my API takes in an Image, validates it and then the image should be stored into a folder. Now for the storage I rely on my
Service. Would it not be better to place my API in my Service project?
If you have other suggestions or improvements feel free to suggest them.2 Replies
Well, the general advice nowadays is to use the vertical slice architecture, not onion or clean :KEKW:
But if you want to stick to this, then it looks good as it is
Hahaha yeah all have their pros and cons and for now I want to just have the job done in some kind of "clean way".
In my service layer I store the image on disk. when I want to change the output directory I need to manually update the code instead of through a config file or docker for example. Do you maybe have tips for that?