Timeline for Domain Driven Design - Updating and persisting aggregates
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 15, 2021 at 9:10 | comment | added | neuro_sys | I agree with "Save the entire aggregate every time it changes regardless of which (possibly nested) fields change". The optimization problem has nothing to do with DDD, and which can be solved separately. | |
| May 6, 2020 at 19:25 | history | edited | user3347715 | CC BY-SA 4.0 | edited body |
| May 6, 2020 at 19:05 | history | edited | user3347715 | CC BY-SA 4.0 | added 4 characters in body |
| May 5, 2020 at 16:48 | comment | added | user3347715 | I'd just like to make a note here that the spirit of this answer is meant to be interpreted as a "kick in the butt" or a "you can do it". I apologize if it reads as condescension. That is not my intent. | |
| May 5, 2020 at 16:45 | history | answered | user3347715 | CC BY-SA 4.0 |