Suggest an editImprove this articleRefine the answer for “What is an "Anemic Domain Model"?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)An **Anemic Domain Model** is an antipattern in which domain objects hold only data, but no behavior: entities are just sets of fields with getters and setters, and all business logic is pushed into services or controllers. **Key point:** the DDD solution is to bring behavior back into the domain, so objects don't just describe data but act as participants in the business process.Shown above the full answer for quick recall.Answer (EN)ImageAn **Anemic Domain Model** is an antipattern in which **domain objects hold only data, but no behavior**. Signs: 1. Entities are just sets of fields with getters and setters. 2. All business logic is pushed into services or controllers. 3. The *Encapsulation* principle is broken: data is "naked," and behavior is smeared around. Example: ```python order.status = "paid" # instead of order.pay() ``` **Problem:** the code loses its connection to business meaning, rules get duplicated, and testing is hard. **DDD solution:** bring behavior back into the domain, so objects *don't just describe data, but act as participants in the business process*.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.