Abstract: A method and system of processing database transactions in a distributed online transaction processing (OLTP) database is provided. Overhead and network bandwidth associated with a global transaction manager are reduced and scalability improved by determining whether incoming statements are single-shard or multi-shard. For single-shard statements, a local transaction identifier (TXID) stored and associated with a data record reference by the statement is retrieved. The retrieved TXID is compared against a copy of a list of prepared transactions that are pending in a respective data node. If the TXID is in the copy of the prepared list, the statement is caused to await until the previous transaction has been committed or aborted. The visibility of a change committed by the previous is then determined, and the statement is processed.

Abstract: A method and system of processing database transactions in a distributed online transaction processing (OLTP) database is provided. Overhead and network bandwidth associated with a global transaction manager are reduced and scalability improved by determining whether incoming statements are single-shard or multi-shard. For single-shard statements, a local transaction identifier (TXID) stored and associated with a data record reference by the statement is retrieved. The retrieved TXID is compared against a copy of a list of prepared transactions that are pending in a respective data node. If the TXID is in the copy of the prepared list, the statement is caused to await until the previous transaction has been committed or aborted. The visibility of a change committed by the previous is then determined, and the statement is processed.

Abstract: The disclosed systems, structures, and methods are directed towards for processing a lock request by a master node to access a shared data object in a database located at a remote location comprising identifying, in the master node, a category of the lock request. If the lock request is for a self-compatible lock, determining a value of a counter associated with the master node and with one or more other master nodes, and if the value of the counter is zero, locally granting the lock request. If the value of the counter is greater than zero, forwarding the lock request to a global lock manager (GLM), and if the lock request is for a heavy-conflicting lock, forwarding the lock request by the master node to the GLM.