Optimistic locking is a method to make sure that the client-side merchandise that you’re updating (or deleting) is identical because the merchandise in DynamoDB. Optimistic concurrency is determined by checking a worth upon save to make sure that it has not modified. Should you use this technique, then your database writes are protected against being overwritten by the writes of others — and vice-versa.
By default, the DynamoDB write operations (PutItem, UpdateItem, DeleteItem) are unconditional: every of those operations will overwrite an present merchandise that has the required major key.
DynamoDB optionally helps conditional writes for these operations. A conditional write will succeed provided that the merchandise attributes meet a number of anticipated situations. In any other case, it returns an error. Conditional writes are useful in lots of conditions. For instance, you may want a PutItem operation to succeed provided that there may be not already an merchandise with the identical major key. Or you might stop an UpdateItem operation from modifying an merchandise if one in every of its attributes has a sure worth. Conditional writes are useful in instances the place a number of customers try to switch the identical merchandise.
Within the AWS SDK for PHP, there’s a PessimisticLockingStrategy class for DynamoDB. This locking technique makes use of pessimistic locking (much like how the native PHP session handler works) to make sure that classes usually are not edited whereas one other course of is studying/writing to it. Pessimistic locking might be costly and may enhance latencies, particularly in instances the place the person can entry the session greater than as soon as on the similar time (e.g. ajax, iframes, or a number of browser tabs).
