Abstract: Disclosed are various embodiments for employing spillover tables that may improve the performance of data store updates. In some embodiments, transaction data that specifies a value by which to adjust a field in a data table is received. The field in the data table is associated with a predefined constraint. An attempt to obtain an exclusive lock for at least a portion of the data table is initiated. Whether the value has a potential to cause the predefined constraint to remain satisfied is identified. The transaction data is stored in a spillover table in response to a failure to obtain the exclusive lock and in further response to the value having the potential to cause the predefined constraint to remain satisfied.

Abstract: Disclosed are various embodiments for employing spillover tables to improve performance of data store updates. A request to update a data field is received, and if an exclusive lock on a data table cannot be obtained, the request is placed in a spillover table until the exclusive lock can be obtained. If the request causes a constraint on the data field to be violated or causes the data field to move closer to the constraint, the request is not placed in the spillover table. A spillover task can collapse entries in the spillover table into the data store when an exclusive lock can be obtained.