Naming convention for domain services and applications with DDD

In the DDD approach, what is best for naming domain service components and application components?

For example, should I have at my application level a service with the name: RoomReservationService and in my domain layer a service called RoomReservationService; first delegation to another?

Actually, when the application service does not collect many domain services, this means that I cannot find different names between them, how can I call it without any confusion?

+3
source share
1 answer

In DDD, you can use the same approach as remote services applications:

Application Level Service Name: RoomReservationService
In the package name:com.my.package.service.RoomReservationService

: RoomReservationDomainService
: com.my.package.domain.service.RoomReservationDomainService

+3

All Articles