<s>
The	O
anemic	B-Architecture
domain	I-Architecture
model	I-Architecture
is	O
described	O
as	O
a	O
programming	O
anti-pattern	O
where	O
the	O
domain	O
objects	O
contain	O
little	O
or	O
no	O
business	B-Architecture
logic	I-Architecture
like	O
validations	O
,	O
calculations	O
,	O
rules	O
,	O
and	O
so	O
forth	O
.	O
</s>
<s>
The	O
business	B-Architecture
logic	I-Architecture
is	O
thus	O
baked	O
into	O
the	O
architecture	O
of	O
the	O
program	O
itself	O
,	O
making	O
refactoring	O
and	O
maintenance	O
more	O
difficult	O
and	O
time-consuming	O
.	O
</s>
<s>
In	O
an	O
anemic	O
domain	O
design	O
,	O
business	B-Architecture
logic	I-Architecture
is	O
typically	O
implemented	O
in	O
separate	O
classes	O
which	O
transform	O
the	O
state	O
of	O
the	O
domain	O
objects	O
.	O
</s>
<s>
This	O
pattern	O
is	O
a	O
common	O
approach	O
in	O
Java	B-Device
applications	O
,	O
possibly	O
encouraged	O
by	O
technologies	O
such	O
as	O
early	O
versions	O
of	O
EJB	B-Language
's	O
Entity	B-Language
Beans	I-Language
,	O
as	O
well	O
as	O
in	O
.NET	B-Application
applications	O
following	O
the	O
Three-Layered	O
Services	O
Application	O
architecture	O
where	O
such	O
objects	O
fall	O
into	O
the	O
category	O
of	O
"	O
Business	O
Entities	O
"	O
(	O
although	O
Business	O
Entities	O
can	O
also	O
contain	O
behavior	O
)	O
.	O
</s>
<s>
An	O
anemic	B-Architecture
domain	I-Architecture
model	I-Architecture
might	O
occur	O
in	O
systems	O
that	O
are	O
influenced	O
from	O
Service-Oriented	O
Architectures	O
,	O
where	O
behaviour	O
does	O
not	O
or	O
tends	O
to	O
not	O
travel	O
,	O
such	O
as	O
messaging/pipeline	O
architectures	O
,	O
or	O
SOAP/REST	O
APIs	O
.	O
</s>
<s>
A	O
common	O
criticism	O
is	O
the	O
idea	O
that	O
anemic	B-Architecture
domain	I-Architecture
model	I-Architecture
makes	O
it	O
easier	O
to	O
follow	O
the	O
SOLID	O
principles	O
:	O
"	O
The	O
‘	O
S’	O
refers	O
to	O
the	O
Single	O
Responsibility	O
Principle	O
,	O
which	O
suggests	O
that	O
a	O
class	O
should	O
do	O
one	O
thing	O
,	O
and	O
do	O
it	O
well	O
(	O
...	O
)	O
"	O
.	O
</s>
<s>
Certain	O
liabilities	O
the	O
programmer	O
must	O
consider	O
are	O
introduced	O
by	O
using	O
an	O
anemic	B-Architecture
domain	I-Architecture
model	I-Architecture
:	O
</s>
<s>
Violation	O
of	O
the	O
encapsulation	B-Application
and	O
information	B-Application
hiding	I-Application
principles	O
.	O
</s>
<s>
Needs	O
a	O
separate	O
business	O
layer	O
to	O
contain	O
the	O
logic	O
otherwise	O
located	O
in	O
a	O
domain	B-Application
model	I-Application
.	O
</s>
<s>
It	O
also	O
means	O
that	O
domain	B-Application
model	I-Application
's	O
objects	O
cannot	O
guarantee	O
their	O
correctness	O
at	O
any	O
moment	O
,	O
because	O
their	O
validation	O
and	O
mutation	O
logic	O
is	O
placed	O
somewhere	O
outside	O
(	O
most	O
likely	O
in	O
multiple	O
places	O
)	O
.	O
</s>
<s>
Needs	O
a	O
service	O
layer	O
when	O
sharing	O
domain	B-Architecture
logic	I-Architecture
across	O
differing	O
consumers	O
of	O
an	O
object	O
model	O
.	O
</s>
<s>
An	O
anemic	B-Architecture
domain	I-Architecture
model	I-Architecture
would	O
have	O
one	O
write	O
code	O
like	O
the	O
following	O
(	O
written	O
in	O
C#	B-Application
)	O
,	O
which	O
by	O
itself	O
does	O
not	O
implement	O
any	O
of	O
the	O
business	O
concerns	O
,	O
in	O
this	O
case	O
,	O
that	O
a	O
height	O
or	O
a	O
width	O
cannot	O
be	O
zero	O
or	O
negative	O
,	O
or	O
that	O
somewhere	O
else	O
there	O
is	O
a	O
requirement	O
for	O
the	O
area	O
of	O
the	O
rectangle	O
.	O
</s>
