Timeline for Locking (reserve) related Aggregate Roots
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 23, 2021 at 14:15 | comment | added | deamon |
The final solution is inspired by your suggestion. The main difference is that the Container doesn't need to know something about the other aggregates. However, this mechanism could still by bypassed like in your example. I don't see a solution that could prevent it properly.
|
|
| Feb 19, 2021 at 13:55 | comment | added | deamon |
I like the idea. Maybe this could be generalized to something like executeInContextOfContainer. But since the passed function would call public methods of PartA or PartB it would still be possible to skip the call to the Container method first.
|
|
| Feb 19, 2021 at 10:24 | history | answered | Robert Bräutigam | CC BY-SA 4.0 |