Domain layer and Application layer separation
urosjarc opened this issue · 1 comments
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
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.