Anaemic domain model

A model that looks object-oriented — a class per concept, carefully named — but holds no behaviour, with all the logic in separate service classes. Fowler named it an anti-pattern because it pays the full cost of the mapping and gets none of the benefit: the data and the rules that protect it are apart, so nothing can enforce an invariant. The honest counter-argument is that for a thin application it is simply a transaction script with more files, and the mistake is claiming it is a domain model.