Timeline for Migration from Anemic Models to Rich Models
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2019 at 18:11 | answer | added | VoiceOfUnreason | timeline score: 4 | |
| Jan 31, 2019 at 17:45 | comment | added | bobek | @bitsoflogic Should the repository be a persistence layer only? Save, Retrieve, Update, Delete the entities? Are you suggesting that I pass the IHttpInvoker to the Save() of Repository? | |
| Jan 31, 2019 at 17:03 | comment | added | bitsoflogic |
If those details need to be triggered every time the email is changed, I would expect the userRepository to be responsible for setting that process in motion. Because that's when the change is actually happening.
|
|
| Jan 31, 2019 at 17:02 | answer | added | user3347715 | timeline score: 3 | |
| Jan 31, 2019 at 16:55 | answer | added | Ewan | timeline score: 1 | |
| Jan 31, 2019 at 16:47 | answer | added | Angus Goldsmith | timeline score: 1 | |
| Jan 31, 2019 at 16:45 | comment | added | bobek |
@bitsoflgic Pretty much yes. But it can get a lot more complicated than that. For example, based on the presence or change of the email I might have to call one of my microservices to do an update. Or trigger a background job. Or wipe my redis cache. Or update some other entities etc. etc.
|
|
| Jan 31, 2019 at 16:43 | comment | added | bitsoflogic |
"I have to write the same code again." What code is re-written? I'm imagining something like user.email = '[email protected]', then userRepository.save(user).
|
|
| Jan 31, 2019 at 16:24 | history | asked | bobek | CC BY-SA 4.0 |