Home/ Questions/Q 8608427
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T03:36:29+00:00

When you are developing an architecture in OO/DDD style and modeling some domain entity

  • 0

When you are developing an architecture in OO/DDD style and modeling some domain entity e.g. Order entity you are putting whole logic related to order into Order entity.
But when the application becomes more complicated, Order entity collects more and more logic and this class becomes really huge.
Comparing with anemic model, yes its obviously an anti-pattern, but all that huge logic is separated in different services.

Is it ok to deal with huge domain entities or i understand something wrong?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s fine to use services in DDD. You will commonly see services at the Domain, Application or Infrastructure layers.

    Eric uses these guidelines in his book for spotting when to use services:

    • The operation relates to a domain concept that is not a natural part of an ENTITY or VALUE OBJECT.
    • The interface is defined in terms of other elements in the domain model
    • The operation is stateless
    • 0