Domain classes (entities) manage their
persistent data, and “rich” ones also provide app-related actions on
their data
Idea of DDD, domain-driven design (Fowler[13],
Evans[14], 2004)
Service layer coordinates actions between entities as needed for transactional actions
Service layer should be thin, delimiting
transactions and calling on domain classes
for most of the work,
Data-only entities dubbed “anemic domain model”