Browse DevX
Sign up for e-mail newsletters from DevX


A Pure Object-oriented Domain Model by a DB Guy, Part 4 : Page 6

This is the fourth in a series of articles by Jimmy Nilsson on a new architecture for enterprise applications in .NET. The new architecture is purely object-oriented, while still focusing on roundtrips and the data access code to get good performance.




Building the Right Environment to Support AI, Machine Learning and Deep Learning

Locating the correct Persistence Class

As a matter of fact, locating the correct persistence class for filling domain objects or saving domain objects is just part of the problem of mapping the relational database to your domain model. You might find this trivial at first, but it’s not. For example, add inheritance to the picture and the problem quickly gets complicated.

Since I haven’t decided on how I want the whole Data Mapper [2] thing yet, I write the mapping code manually and explicitly for now.

The Data Mapper pattern discusses (typically) how an object-oriented domain model interacts with a relational database.

When I have decided how I want the Data Mapper code, I have several different mechanisms from which to choose. First I have to decide on where to hold the meta data that I need for mapping between the domain model and a relational database:

  • Attributes
  • File

Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date