tag:blogger.com,1999:blog-3406666181435971572.post2109102980986911330..comments2009-05-24T18:17:48.674-05:00Michael Brennanhttp://www.blogger.com/profile/09351708784127332440noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3406666181435971572.post-11829205466919528362009-05-24T18:17:48.674-05:002009-05-24T18:17:48.674-05:00I have, DDD services are not the services Fowler speaks of in ADM. The anti-pattern is to extract the behavior into services that form a separate layer on top of the domain model layer. This is bad, since we're now expressing domain logic outside of the domain model layer. Furthermore, this service layer starts to become fat, instead of being kept thin.<br /><br />It's also important to keep in mind that most behavior should be encapsulated inside entities and value objects. DDD services should generally be used for interaction between the two. Too much behavior in a DDD service should be a design smell as well.Michael Brennanhttp://www.blogger.com/profile/09351708784127332440noreply@blogger.comtag:blogger.com,1999:blog-3406666181435971572.post-61888000421639465932009-05-24T16:12:35.189-05:002009-05-24T16:12:35.189-05:00This is the way I program but I'm curious if you've ever read Fowler's article on the Anemic Domain Model:<br /><br />http://martinfowler.com/bliki/AnemicDomainModel.htmldigidhttp://www.blogger.com/profile/07033507154839181474noreply@blogger.com