This question was included in the original "Lazy Loading" post, but
is really a separate topic:

>3. There seem to be some systems that, when modeled, do not reveal
>much business logic at all, instead appearing to be glorified data
>structures. Are these models served better without DDD? I want the
>answer to this question to be 'no', but i also want to avoid trying
>to solve every problem with the same solution.

I agree with you that domain-driven design is not the best approach
to everything. The "smart-ui", is one approach to a certain class of
programs without complex behavior. The "transaction script" in
Martin Fowler's PEAA is another.

A model is something more than data, but certain parts of my book do
apply to any project with a moderately complicated database schema.
Knowledge crunching, bounded context, and ubiquitous language come
to mind. But the main focus of DDD is on applications that have
complex behavior or rules applying to the relationship of the data.

Of course, if we looked for it, I think we might find opportunities
to build more valuable software with interesting behavior in many of
these seemingly data-oriented applications.

EricEvans


DataOrientedSystemsAndDDD is mentioned on: ThreadView