Applying Domain-Driven Design and Patterns: With Examples in C# and .NET

Chapter 8. Infrastructure for Persistence Where are we? We have built a Domain Model from the ground up, and it's in DDD [Evans DDD] style. So far, I've been pushing like crazy for delaying the decisions about infrastructure as long as possi...

Requirements on the Persistence Infrastructure Let's repeat again that I want the infrastructure to stay out of the way of the Domain Model as much as possible so that I can focus on creating a powerful Domain Model for solving the business proble...

Where to Store Data Assume we start with a clean sheet of paper; how would we like to store the data? We have at least four choices: RAMFile systemObject databaseRelational database Note I realize that this may be a case of apples and oranges...

Approach There are certainly many different ways of dealing with the Data Mapper pattern, but I think the most typical are the following: Custom manual codeCode generation of custom codeMetadata mapping (O/R Mapping) Let's start discussing custo...

Classification Let's have a closer look at what an O/R Mapper is. We'll discuss this from two different angles. First, we'll discuss it from one dimension: different characteristics. Next, we'll discuss it from some of the PoEAA patterns that ar...

Another Classification: Infrastructure Patterns In this second part of the classification, I will use some of the PoEAA patterns [Fowler PoEAA], some of which are focused on infrastructure. Again, this description can be used even if you decide t...

Summary Now we have discussed the need for persistent infrastructure to some extent. After having introduced the subject and defined some requirements on the needed persistent infrastructure, we discussed the subject from different angles such as ...