Detecting Concurrent Writes

[mpluecker]

Since the pattern query an object -> modify -> update is not atomic, whenever updates of the same object happen simultaneously, data may be lost. This can happen because of a distributed system nature and multi-threading within a single server.
Thus, we want to detect concurrent writes, i.e. the second write request should fail. This can be accomplished by storing a revision for each entity in the database which is strictly increasing with every write access. When updating an entity, the driver then checks that the revision has not changed between querying the object and updating it.

[remi128]

annotation revision marks the field to be used
usage of https://dzone.com/articles/jpa-20-concurrency-and-locking