It can be harder to distinguish application SERVICES from domain SERVICES. The application layer is responsible for ordering the notification. The domain layer is responsible for determining if a threshold was met—though this task probably does not call for a SERVICE, because it would fit the responsibility of an “account” object. That banking application could be responsible for funds transfers. If a SERVICE were devised to make appropriate debits and credits for a funds transfer, that capability would belong in the domain layer. Funds transfer has a meaning in the banking domain language, and it involves fundamental business logic. Technical SE...
- Five. A Model Expressed in Software
- from Domain-Driven Design: Tackling Complexity in the Heart of Software
- Publisher: Addison-Wesley Professional
- Released: August 2003
Application vs Domain layer services
Share this highlighthttp://www.safaribooksonline.com/a/domain-driven-design-tackling/329590/