domain service

in the Domain Driven Design project structure I call this "Application"

• encapsulates processes/policies
• orchestrates entities
  • avoid anemic domain models
• part of ubiquitous language
• domain services are stateless (the state is in the entity)

1. service looks up entities
2. entities mark their points as expired
3. service persists

gets and stores state, and explains what actions to take, but not how the actions work

possibly related to functional programming