0

Developing n-layered application with DDD (o better DDDD because we are using WCF) using Microsoft technology (where we have full controll of all component), the best choise seems to be STE vs POCO (this last one force the usage of DTOs). That's right? In your opinion make sense the usage of STE with DTOs where we need them?

Thanks.

Andrea
  • 803
  • 1
  • 12
  • 27
  • 2
    Using WCF does not make it DDDD. I recommend you (re)read Eric Evans book and watch every video of Udi Dahan and Greg Young and Eric Evans on the subject. It should give you an idea of what building software using (D)DDD is about. A few videos [here](http://skillsmatter.com/podcast/design-architecture/talk-from-udi-dahan) and [here](http://www.infoq.com/presentations/ddd-eric-evans). – Iulian Margarintescu Jun 23 '11 at 07:55
  • I know perfeclty that Eric Evans, in his book about DDD, almost entirely avoids the issue on distributed technologies and systems (Web services, etc.) because it is mainly focused on the Domain. However, the distributed systems and remote Services are something we need in most scenarios. Four „Ds‟? Well, yes, it is clear that DDDD is an evolution/extension of DDD where distributed systems aspects are added. – Andrea Jun 23 '11 at 08:02

1 Answers1

0

I really can recommend Julie Lerman's Programming Entity Framework. She goes in depth about simple poco's, dto's and Self Tracking Entities. Advantages and disadvantages are described. But off course depending a lot on application requirements and personal taste.

So I can't give you an exact answer because the question is to general for that. But reading the book should give you a taste of the possible alternatives and can help you in making these kind of design decisions. I'm working with Self Tracking Entities in combination with a Business Access Layer, Serive Layer, WCF, Win / WPF clients. And expanding it in the future most probably with ASP.NET

Youp Bernoulli
  • 5,303
  • 5
  • 39
  • 59