Timeline for How to model parallel processes (in a Bounded Context) with the same data store?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 26, 2015 at 21:58 | comment | added | FastAl | If you are going to await, might as well not bother eagerly creating the UI element unless you have extra time on your hands ;-) You'll still be creating a maintenance/update legacy even then. | |
| Jan 24, 2015 at 15:49 | comment | added | Alexander Langer | I agree. More specifically, any event-driven CQRS-style architecture where the background process accepts commands and emits events about changes that are only shown read-only by the UI will do. | |
| Jan 24, 2015 at 14:49 | comment | added | ctietze | So the control panel shouldn't create containers itself but send commands to the background process, so there's only one writer? Then it awaits an update with the new data. Okay. I'd then create the element eagerly in UI for fast feedback and wait for confirmation of the background process instead. Could you elaborate on the benefits (last paragraph) a bit more? | |
| Jan 24, 2015 at 2:35 | history | answered | FastAl | CC BY-SA 3.0 |