All geek questions in one place

Developing a domain model by level using the Entity Framework

We are in the process of developing a domain model for a new application. The application consists of three layers. Some of the objects are common to all layers, where some of the other objects are unique to a certain level. A unique object may contain a link or reference a shared object. The code associated with unique objects will also be unique to this layer. We will use Entity Framework 4.0 for persistence, with POCO.

What are our options regarding:

  • Should we split the domain up? If so, this would mean that we could not have references to non-shared entities within common entities, and as such would have to expose the business logic associated with that entity.
  • If we divide the domain at all levels, can we define separate Entity Framework models for each level, since each level has its own repository?

Any thoughts on any approach and best practices that should be followed will be appreciated.

Many thanks

+3
source share
1 answer

I would have one model project - with your POCOs. This project can be referenced by any layer.

+1
source

Source: https://habr.com/ru/post/1786118/

More articles:


All Articles