Tactical Patterns: Services, Use Cases, and Transactions

Distinguish between Domain Services (for domain logic spanning multiple aggregates) and Application Services (for orchestrating use cases)

Implement a stateless Domain Service for complex business rules that do not naturally fit within an entity or value object

Implement an Application Service to handle a specific user-facing use case by coordinating domain objects and repositories

Use the Unit of Work pattern within an Application Service to ensure atomic operations across one or more repositories