Place infrastructure Entity 4.0 + POCO + WCF in DDD "world"

Question

I try to understand. In the DDD approach, we have a presentation layer (UI), an application layer (application services), a domain layer, and an infrastructure. I'm sure someone knows a short description of these 4 layers.

I know the WCF steps in the Application area and the Entity Framework.edmx model at the infrastructure level.

Now a "silent riddle" has appeared: where do I need to put POCO objects, interfaces and repository implementation? I can use POCO objects, such as domain model objects, given the constant ignorance of POCO, or it is better to have other objects in the domain model and map these objects over POCO objects.

I read several articles, but in most EF4 and POCO they are presented in very simple situations where it is impossible to single out the real advantage of using EF4 and POCO, for this I want your points of view.

Many thanks!

Answer 1

POCO may be the subject of your domain because it is clueless. I see no reason to create a separate set of objects for saving and a separate set for domain objects. The repository is part of the infrastructure layer.