Timeline for Locking (reserve) related Aggregate Roots
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 23, 2021 at 14:10 | answer | added | deamon | timeline score: 0 | |
| Feb 22, 2021 at 15:20 | history | edited | deamon | CC BY-SA 4.0 |
add reason why events are only partial solution
|
| Feb 19, 2021 at 12:04 | comment | added | deamon |
The user would typically hold the lock for up to a few hours. The use can only lock Container and there are no relationships between Container instances. So the number of locked containers has no relevance in this context.
|
|
| Feb 19, 2021 at 10:24 | answer | added | Robert Bräutigam | timeline score: 1 | |
| Feb 19, 2021 at 9:58 | comment | added | Bart van Ingen Schenau | For how long can a user hold a lock on a set of aggregate roots? Is the set to lock pre-determined or does the user get to choose which roots to lock? What should happen if a user wants to edit two roots, one of which is locked? Can you design the system such that a user must explicitly lock the affected roots before any modification is accepted (i.e. only the user holding the lock is allowed to modify)? | |
| Feb 19, 2021 at 9:18 | history | edited | deamon | CC BY-SA 4.0 |
added 2 characters in body
|
| Feb 19, 2021 at 8:19 | history | asked | deamon | CC BY-SA 4.0 |