Timeline for Anemic Models vs. Rich Models: When to Use?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3 at 16:59 | comment | added | Ewan | Not really, For example order.Buy() order.Dispatch(). both use the same data set, but the operations are too different in terms of their dependencies and user scope to fit on the same class. If you want to use "different" domain models, you end up with abstract Order with all the properties, OrderForBuying : Order and OrderForDispatching : Order | |
| Oct 3 at 2:34 | comment | added | Flater | I feel the "when you have more than one operation" is an unfair comparison. If A and B are that distinct that you'd create separate services for them, you're probably not going to want to start piling them into the same domain model (as a matter of OCP adherence). If A and B are closely related enough that it'd be reasonable for them to be added to the same domain model, then you'd also expect it to be reasonable to add them to the same service. | |
| Oct 2 at 22:03 | history | edited | Ewan | CC BY-SA 4.0 |
added 934 characters in body
|
| Oct 2 at 21:46 | history | answered | Ewan | CC BY-SA 4.0 |