Ok, “CQRS! DDD!” (Those buzzwords must ring a couple of bells)
One of the largest problems seen in “A Stereotypical Architecture” was
that the intent of the user was lost. Because the client interacted by posting
data-centric DTOs back and forth with the Application Server, the domain was
unable to have any verbs in it. The domain had become a glorified abstraction
of the data model. [..]
Many examples of such applications can be cited. Users have “work flow”
information documented for them. Go to screen xyz edit foo to bar, then go
to this other screen and edit xyz to abc. For many types of systems this type
of workflow is fine. These systems are also generally low value in terms of
the business. In an area that is sufficiently complex and high enough ROI
in order to use Domain Driven Design these types of workflows become unwieldy.
