Plain Old CLR Objects

Abstract

Objects should not know how to save themselves, load themselves, or filter themselves. That’s a familiar mantra in software development, and especially in Domain Driven Development. There is a good bit of wisdom in this mantra. Having persistence knowledge bound too tightly to domain objects complicates testing, refactoring, and reuse. In ObjectContext, the classes generated by Entity Framework for model entities are heavily dependent on the plumbing of Entity Framework. For some developers, these classes know too much about the persistence mechanism, and they are too closely tied to the concerns of models and mapping. There is another option, however.