Question

Is it possible to use DDD and a rich domain model if your application is like:

• windows client (WPF)
• windows service

And communication happens with WCF?

I’m used to have DTO’s with only data state, and have business rules inside the Service layer, but everyone keeps telling me that I should have a rich domain model where data state and rules/methods are all in the objects themselves.

I’m just not sure if this rich domain model would apply to a system that has a UI and communicates via WCF to a service (like I presented above). In my case is it better to continue using an anemic domain model because of WCF? If not, could you please give an example on how to architecture it using a rich domain model, considering WCF, proxy, etc?

Thanks!

Answer 1

Generally speaking you serialize your domain objects for transmission across WCF as some simplified DTO anyway, and it’s these that are consumed by your client application.

You can serialize user defined types and deserialize them in the client but for most applications this is unnecessary. As long as you don’t need the ‘rich’ behaviour of your objects in your client (which you shouldn’t with a good DDD anyway), it sounds to me like you are fine to use a rich design in your service layer and send simple DTOs across the wire.