Reactive transaction management

A method comprising:

• receiving, by an application framework, a program that defines a transaction having a plurality of operations to one or more respective transactional resources;
• generating, by the application framework, a respective sequence of reactive operators for each transactional resource in the transaction;
• initiating each respective sequence of reactive operators, including:
• storing transaction metadata in a subscription context for the sequence,
• evaluating the sequence of reactive operators in an upstream subscription flow ordering until evaluating an operator that connects to the transactional resource, and passing the subscription context for the sequence to each subsequent operator in the sequence, and
• evaluating the sequence of reactive operators in a downstream data flow ordering when the operator that connects to the transactional resource begins receiving data;
• determining, by the application framework using a first thread, that one of the sequences has not completed;
• in response to the determining that one of the sequences has not completed, relinquishing computing resources of the first thread;
• receiving an indication that all of the sequences of reactive operators have completed;
• determining whether none of the sequences of reactive operators failed;
• and
• in response to determining that none of the sequences of reactive operators failed, committing the operations of the transaction in each of the one or more transactional resources.

One or more computer-readable storage media encoded with instructions that, when executed by one or more computers, cause the one or more computers to perform operations comprising:

• receiving, by an application framework, a program that defines a transaction having a plurality of operations to one or more respective transactional resources;
• generating, by the application framework, a respective sequence of reactive operators for each transactional resource in the transaction;
• initiating each respective sequence of reactive operators, including:
• storing transaction metadata in a subscription context for the sequence,
• evaluating the sequence of reactive operators in an upstream subscription flow ordering until evaluating an operator that connects to the transactional resource, and passing the subscription context for the sequence to each subsequent operator in the sequence, and
• evaluating the sequence of reactive operators in a downstream data flow ordering when the operator that connects to the transactional resource begins receiving data;
• determining, by the application framework using a first thread, that one of the sequences has not completed;
• in response to the determining that one of the sequences has not completed, relinquishing computing resources of the first thread;
• receiving an indication that all of the sequences of reactive operators have completed;
• determining whether none of the sequences of reactive operators failed;
• and
• in response to the determining that none of the sequences of reactive operators failed, committing the operations of the transaction in each of the one or more transactional resources.