Timeline for What is a good domain model in this case?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 13, 2019 at 9:01 | history | edited | Robert Bräutigam | CC BY-SA 4.0 |
deleted 12 characters in body
|
| Dec 13, 2019 at 0:14 | comment | added | inf3rno | This track sounds a lot better, thanks! :-) | |
| Dec 12, 2019 at 21:39 | history | edited | Robert Bräutigam | CC BY-SA 4.0 |
added 683 characters in body
|
| Dec 12, 2019 at 21:19 | comment | added | inf3rno | The question is mostly about how to model the interaction between the grid and the objects. The grid contains the information necessary to calculate the value for a certain position and the object contains the position and maybe the previously calculated value for that position. The whole grid and the position for an object can be updated independently and in both cases the values are updated for one or more objects. If both the grid and the object are domain objects, then which one should be the aggregate root? The interface you gave just does not answer this question... | |
| Dec 12, 2019 at 21:13 | comment | added | inf3rno | "Also, I don't get why the positions of "objectid" needs to be tracked, there doesn't seem to be any behavior for that from what I understand." - The positions need to be tracked, because when I update the grid I need to calculate the values for each object again based on the new grid and their position. | |
| Dec 12, 2019 at 21:12 | comment | added | inf3rno | "I don't know what the purpose of changing the grid's values would be. I would just replace the object when values change, if there is nothing else that disallows it." - It is ok to replace the grid with a new one. Just keep in mind that we can optimize the code if we check the difference between the old and the new grid and calculate new values only for the objects which are near to grid changes. | |
| Dec 12, 2019 at 21:02 | history | answered | Robert Bräutigam | CC BY-SA 4.0 |