How does DDD help avoid "anemic" models?

DDD requires behavior to live together with data. In "anemic" models, objects are just containers of fields, and all the logic is pushed into services.

DDD does the opposite:

• entities (Entity) and value objects (Value Object) contain their own methods describing business actions;
• the code reflects real processes ("pay an order," "reserve a product"), not CRUD operations.

Result: the model becomes "alive": business logic is concentrated in the domain instead of being smeared across layers.