Stereotypical Architecture

[Matthieu GD]

I have a problem with the first diagram in your document "A
Stereotypical Architecture". It reads like :

UI -- Remote Facade -- Application Services -- Domain Object -- Data
Storage

You describe here a typical (but no-DDD) architecture, am I right ?
So, why are you using Application Services which is a term related to
DDD ?

My view of the typical architecture which lead to anemic domain will
be more like that :

UI -- Services -- Business -- Domain Objects -- Data Storage

And sometimes there's no DTO for simple applications where the domain
objects are transversal to all layers, so the simplicity is even
greater. It's straightforward for most junior for this reason : you do
CRUD operations with your domain objects directly and you send them to
the service/business layers where the business rules are applied on
them.

I like the way you show that DDD is not applicable and the problem of
Anemic Model.

Matthieu

A minor remark : it's Tomcat, not TomCat :)