Optimistic locking, also referred to as optimistic concurrency control, allows multiple concurrent users to attempt to update the same resource. There are two common ways to implement optimistic locking: version number and timestamp. Version number is generally considered to be a better option because the server clock can be inaccurate over time. We explain how optimistic locking works with version number.