Can't see the architecture discussed on LinkedIn about max_clean_arch HOT 3 CLOSED

Hello, Sébastien!

Original (deprecated) version of the project is available here:
https://github.com/maxeema/max_clean_arch/tree/master/old/max_clean_arch

Kind regards,
Max

from max_clean_arch.

Sebastien

There were some circumstances why there is no history of the project available.

What about the new code-base. Yes, it's pretty different. And the main difference is that the data and domain layers are extracted as independent modules into the "packages" folder.

Thus, in the proposal, there is only one domain. And you can see it as navigation_repository with its contract and models in "packages".

Data layers: web_app_navigation_repository and in_memory_navigation_repository implement the repository and provide data from different sources.

I would say that the lib folder is the implementation of the presentation layer that utilizes domain and data.

Also, I updated/added links in the article and READMEs accordingly.

Kind regards,
Max

from max_clean_arch.

Many thanks for this answer.

Some thought about your changes:

• I agree with the idea to create dedicated module for the data and domain layers. That's make them reusable if needed, and force developers to embrace the clean architecture (no possibility to make a wrong implementation). 👍
• However I don't understand why you don't have a domain package and a data one. Finding models inside the repository folder doesn't seems to be the right thing in a real app. Imagine you've got a user model. You will probably have to use it accross multiple repository and/or use cases (getProductOfUser, getPetOfUser, ...). What have motivated you do do these changes?

from max_clean_arch.