Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Domain layer and Application layer separation #51

Open
urosjarc opened this issue Dec 5, 2018 · 1 comment
Open

Domain layer and Application layer separation #51

urosjarc opened this issue Dec 5, 2018 · 1 comment

Comments

@urosjarc
Copy link

urosjarc commented Dec 5, 2018

Hi, one question related to domain project/module...
Can you explain a little bit more what is a reason that use-cases and domain logic are in
the same module, shouldn't it be more appropriate to separate use-cases to application layer
and domain entities with all their logic to domain layer... This way the domain layer is
shareable as enterprise-wide rules....

More on stackexchange: Application layer vs Domain layer

@urosjarc urosjarc changed the title Domain vs Application layer separation Domain layer and Application layer separation Dec 5, 2018
@qwertyfinger
Copy link

Domain layer is not supposed to contain enterprise-wide rules, this is embedded in its very name itself.
Usual Android approach to Clean Architecture is simplified comparing to the original concept as generally you don't have a set of business logic that many applications need to share.
But, of course, you can incorporate such a layer in a separate module if you need to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants