22.6. Optimistic concurrency control (OCC)

The premise on which the use of OCC is based is that conflict is unlikely to happen. It is also assumed that transactions require high availability of objects, such as in systems which have some degree of real-time requirement. A transaction is allowed to proceed without delay on shadow copies of objects. No changes are applied to persistent object states until the transaction requests commit. The transaction is then validated in order to ascertain whether its shadow copies represent a consistent system state and whether its history is serializable with the histories of transactions that have already ...

Get Operating Systems: Concurrent and Distributed Software Design now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.