While reading Greg Young's post on the topic of the ubiquitous language and behavior driven development, something stuck out at me. I am quoting Greg who is quoting Eric Evans:
Alas, I too have had stakeholders such as what Scott describes. In fact thinking back many of them were in the sorts of domains that I would not recommend DDD and recently Eric Evans has also had had this discussion.
I became more and more aware that one of the basic mistakes that model enthusiasts made from the start was the idea that we should just model everything, that the whole system should modeled and object oriented and so on. what I have started to realize is that that dilutes the effort to the point where we don't really ever get the bang for the modeling buck and that in fact most systems are probably 90% CRUD (create, read, update, delete) and that there are simpler solutions to that problem.
I'll leave you with this thought:
Pragmatism without context is really dogma in disguise. We learned this long ago when defining software patterns. There is a higher level of understanding which exists of nearly everything. You will know you've reached that level of understanding after you have fully understood the item, and then understood it's limitations. Until you can grasp the limitations, be wary of the dogma effect.
That being said, I do think the domain model pattern is grossly underused in the enterprise application space.