How to handle database concurrency

Add version
optimistic locking lock-free, Client A read v1, v2 modified after its set, Client B read v2, v1 is not the same as before (because you want to change it would have been v2 is the client B) in order to distinguish
only increase unabated, as long as it was found a large update than the original version, we need to consider carefully