Domain Use Case

by grzegorz.kosciolek   Last Updated January 02, 2019 16:05 PM

In my understanding of Uncle's Bob Clean Architecture, a Use Case (Interactor) is responsible for orchestrating the Entities. At the same time, it represents Application-specific rules. The business rules live in Entities.

I have a need to orchestrate the Entities to achieve a Business-specific rule. What is the best approach for it?

  1. Is it allowed to have a Use Case in the Domain layer (rather than in the Application layer) to indicate that this use case is business rules, not application rules?
  2. Or should I simply create another Entity that will do the orchestration?


Related Questions



Inject package protected (internal) classes at runtime

Updated December 19, 2018 13:05 PM

Use case interactions in clean architecture

Updated December 09, 2018 02:05 AM