Skip to main content

I think your approach itsis on the right direction, one. One important thing,: your domain model itsis not the Sprite class, your domain its but the SpriteWhatever class!. A real domain model itsis the place withwhere your business rules and behaviors are located, and in. In your example, this is the SpriteXXX class, the. The Sprite class itsis only a data structure for carry oncarrying data, off. Of course this class is anemic, because data structurestructures are anemic by definition.

I think your approach its on the right direction, one important thing, your domain model its not the Sprite class, your domain its the SpriteWhatever class!. A real domain model its the place with your business rules and behaviors are located, and in your example this is the SpriteXXX class, the Sprite class its only a data structure for carry on data, off course this class is anemic, because data structure are anemic by definition.

I think your approach is on the right direction. One important thing: your domain model is not the Sprite class but the SpriteWhatever class! A real domain model is the place where your business rules and behaviors are located. In your example, this is the SpriteXXX class. The Sprite class is only a data structure for carrying data. Of course this class is anemic, because data structures are anemic by definition.

Source Link
AlfredoCasado
  • 2.2k
  • 12
  • 11

I think your approach its on the right direction, one important thing, your domain model its not the Sprite class, your domain its the SpriteWhatever class!. A real domain model its the place with your business rules and behaviors are located, and in your example this is the SpriteXXX class, the Sprite class its only a data structure for carry on data, off course this class is anemic, because data structure are anemic by definition.