backendconcurrencydatabases
Concurrent read-modify-write can lose an update
Anonymous
If two requests read the same value and then both write an incremented value, one increment can disappear. An atomic database update avoids that read-then-write gap. A version check can work too, but a conflict then needs a retry or a clear error; choose based on contention and retry cost.
0