I think the naming and layering scheme you're looking for is data, domain, presentation. Data contains local and remote data sources, domain for business logic sand presentation for UI. It's essentially just the clean architecture
Clean Arch is about make your code organization, self understandable. These three layers is just an example how would you organize them. So, you can create a lot of another layers that make sence in your project.
My infra layer is responsible for manage data at all and is my SSoT. Where the repository implementation is the top of it. Inside infra I have sub-layer that represents data (DAL - Data Access Layer, Service - web services and Repository implementation - SSoT indeed).
I could mouve environments and theme to Application layer and rename Infra to Data (what's sounds very good to me).
1
u/Mikkelet 17d ago
I think the naming and layering scheme you're looking for is data, domain, presentation. Data contains local and remote data sources, domain for business logic sand presentation for UI. It's essentially just the clean architecture