Techniques for concurrent data value commits

A computing device comprising:

• a processor;
• and
• a memory including instructions that, when executed with the processor, cause the computing device to, at least:
• receive a plurality of transactions from one or more client applications, each of the plurality of transactions having an identifier value of a plurality of identifier values;
• conduct a conflict check by determining whether a first identifier value of the plurality of identifier values that corresponds to a first transaction of the plurality of transactions matches a second identifier value of the plurality of identifier values that corresponds to an already committed transaction, the already committed transaction stored in a commit queue;
• and
• in accordance with no match being determined:
• maintain, in relation to transactions in the commit queue, an index value associated with a current latest-completed transaction, at least two of the transactions in the commit queue being committed in parallel;
• store mutations of at least a subset of the transactions in a cache memory, the cache memory configured to store the mutations prior to at least one of being written to a mutation log or being included in a data store snapshot;
• detect that a first transaction of the transactions in the commit queue has been committed;
• determine whether at least one second transaction of the transactions in the commit queue is an intermediary transaction to the first transaction;
• upon determining that no second transaction of the transactions in the commit queue is an intermediary transaction to the first transaction, update the index value to an identifier for a new latest-completed transaction;
• receive an operation to be performed in relation to the transactions in the commit queue;
• and
• perform the operation on the transactions in the commit queue having an identifier value less than or equal to the index value.

A non-transitory computer readable medium storing specific computer-executable instructions that, when executed by a processor, cause a computer system to at least:

• receive a plurality of transactions from one or more client applications, each of the plurality of transactions having an identifier value of a plurality of identifier values;
• conduct a conflict check by determining whether a first identifier value of the plurality of identifier values that corresponds to a first transaction of the plurality of transactions matches a second identifier value of the plurality of identifier values that corresponds to an already committed transaction, the already committed transaction stored in a commit queue;
• and
• in accordance with no match being determined:
• maintain, in relation to transactions in the commit queue, an index value associated with a current latest-completed transaction, at least two of the transactions in the commit queue being committed in parallel;
• store mutations of at least a subset of the transactions in a cache memory, the cache memory configured to store the mutations prior to at least one of being written to a mutation log or being included in a data store snapshot;
• detect that a first transaction of the transactions in the commit queue has been committed;
• determine whether at least one second transaction of the transactions in the commit queue is an intermediary transaction to the first transaction;
• upon determining that no second transaction of the transactions in the commit queue is an intermediary transaction to the first transaction, update the index value to an identifier for a new latest-completed transaction;
• receive an operation to be performed in relation to the transactions in the commit queue;
• and
• perform the operation on the transactions in the commit queue having an identifier value less than or equal to the index value.