Unstable read / write versus read / write in sleep mode?

Question

The above statement is http://docs.jboss.org/hibernate/core/3.3/reference/en/html/performance.html#performance-cache-nonstrict

If the application only occasionally needs to update data (i.e. if it is extremely unlikely that two transactions will try to update the same item at the same time)

What I got from the above statement is if the developer updates the object in his code, sometime he wants to update it in the second-level cache, but someday he doesn't. Correctly? If so, how will he achieve this in his code. I mean, where he needs to indicate in his code that this time he wants to update in the cache at another time.

Answer 1

You are wrong. What does this mean if this strategy is to be used when an entity is sometimes updated (so it is not read-only), but it is highly unlikely that two concurrent transactions update the same element. For example, if you have thousands of users accessing data, one batch updates them regularly, this option is correct: only one transaction updates items at a time.