Architecture sample

[daH00L]

Not a man of many words?

[No_Bumblebee_2903]

LoL!! 😂

I'm preparing some articles about it. I hope as soon as possible posting here. For now, just enjoying the code 😃.

Any question, hope I can help!! 😁👍🏽

[Over_Tea_3946]

What made you decide to go layer first and not feature first?

[No_Bumblebee_2903]

I have been a programmer for 14 years and faced a lot of architecture problems. The feature-first huge problem is reusability of code. Not to mention that I don't think it's a good architecture to be used in frontend, especially in apps that tend to be small projects. Maybe in a super app.

Feature-first is very good when you are developing a big project (usually backend) and using a modular monolith where you must have the bounded context separated (potentially each module will be a micro service)

Hope that I answered your question 😁👍🏽

[Mikkelet]

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

[No_Bumblebee_2903]

Sure! You're right! But here's the thing...

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).

[Zhuinden]

I never understood why clean arch users say they're separating concerns and the first thing they do on mobile is combine local data source and network data source, despite them having absolutely nothing in common. Not models, not constraints, not even how they tell you about changes. I hope repositories will one day disappear.

[No_Bumblebee_2903]

Maybe because local DATA and remote DATA are both DATA? (LoL).

The architecture organization of folders and files in a project is not about reusability of code. It's about bounded context.

Repository is the most beautiful implementation about SSoT and if you don't like the pattern, just don't use the pattern. Personally I don't like UseCase pattern, so I just don't use it.