Cloud-based architecture for processing distributed transactions

A system comprising:

• a plurality of backend nodes communicatively coupled to the storage;
• a distributed query processor (DQP) configured to perform the following operations:
• receiving a distributed execution statement, the distributed execution statement including a plurality of tasks for executing a distributed transaction;
• assigning a quantity of the plurality of backend nodes for executing the plurality of tasks;
• requesting a first backend node from the assigned quantity of the plurality of backend nodes to execute a first task of the plurality of tasks;
• requesting a second backend node from the assigned quantity of the plurality of backend nodes to execute a second task from the plurality of tasks;
• receiving, from the first backend node, a first confirmation that the first task has been executed, the execution of the first task providing a first result, the first confirmation indicating that the first result is ready to be committed by the DQP;
• receiving, from the second backend node, a second confirmation that the second task has been executed, the execution of the second task providing a second result, the second confirmation indicating that the second result is ready to be committed by the DQP;
• executing a conflict check between the first result and the second result;
• and
• based on determining the first result does not conflict with the second result, committing the distributed transaction.

A computer storage medium having computer-executable instructions that, when executed by a distributed query processor (DQP) implemented on a processor, cause the processor to perform the following operations:

• receiving a distributed execution statement, the distributed execution statement including a plurality of tasks for executing a distributed transaction;
• assigning a quantity of backend nodes for executing the plurality of tasks;
• requesting a first backend node to execute a first task of the plurality of tasks;
• requesting a second backend node to execute a second task from the plurality of tasks;
• receiving, from the first backend node, a first confirmation that the first task has been executed, the execution of the first task providing a first result, the first confirmation indicating that the first result is ready to be committed by the DQP;
• receiving, from the second backend node, a second confirmation that the second task has been executed, the execution of the second task providing a second result, the second confirmation indicating that the second result is ready to be committed by the DQP;
• executing a conflict check between the first result and the second result;
• and
• based on determining the first result does not conflict with the second result, committing, by the DQP, the distributed transaction.