3 ms·
I've written plenty systems that would be fine with a valid, consistent but maybe slightly older state (for example when the db describes both work to be done a
by wongarsu 4y ago
I've written plenty systems that would be fine with a valid, consistent but maybe slightly older state (for example when the db describes both work to be done and work results, or the db otherwise implicitly records where to resume work). On the other hand there are obvious examples where this is unacceptable, say recording the transactions of a cash register.
- gpderetta 4y agoI have done as well! My concern is the assertion that this behavior is reasonable for the vast majority of applications.