Abstract: A transactional replicator applying group commit and barrier concepts is disclosed. Group commit means that the transactional replicator commits multiple transactions in a group and is not restricted to committing single transactions one-at-a-time and is not limited to operating on a single state provider. Barrier means that the transactional replicator does not move forward to commit additional transactions until the previous group of transactions are completed. All state providers must apply their transactions and update state before additional transactions will be committed. A quorum acknowledgement “unlocks” any locks that were acquired to update the state within a state provider. However, as long as there are no lock conflicts, additional transactions can continue to create new group commits as necessary.

Abstract: Various techniques for distributed storage of state information in a computing fabric are disclosed herein. In one embodiment, a method includes executing a software application at a computing device of a computing fabric, and thus resulting in a change to a portion of a copy of state information associated with the software application stored in the computing device. The method also includes automatically replicating the change to the portion of the copy of state information stored on the computing device to one or more other computing devices in the computing fabric. The one or more other computing devices individually contain a copy of the state information associated with the software application.

Abstract: A transactional replicator applying group commit and barrier concepts is disclosed. Group commit means that the transactional replicator commits multiple transactions in a group and is not restricted to committing single transactions one-at-a-time and is not limited to operating on a single state provider. Barrier means that the transactional replicator does not move forward to commit additional transactions until the previous group of transactions are completed. All state providers must apply their transactions and update state before additional transactions will be committed. A quorum acknowledgement “unlocks” any locks that were acquired to update the state within a state provider. However, as long as there are no lock conflicts, additional transactions can continue to create new group commits as necessary.

Abstract: A transactional replicator applying group commit and barrier concepts is disclosed. Group commit means that the transactional replicator commits multiple transactions in a group and is not restricted to committing single transactions one-at-a-time and is not limited to operating on a single state provider. Barrier means that the transactional replicator does not move forward to commit additional transactions until the previous group of transactions are completed. All state providers must apply their transactions and update state before additional transactions will be committed. A quorum acknowledgement “unlocks” any locks that were acquired to update the state within a state provider. However, as long as there are no lock conflicts, additional transactions can continue to create new group commits as necessary.

Abstract: Various techniques for distributed storage of state information in a computing fabric are disclosed herein. In one embodiment, a method includes executing a software application at a computing device of a computing fabric, and thus resulting in a change to a portion of a copy of state information associated with the software application stored in the computing device. The method also includes automatically replicating the change to the portion of the copy of state information stored on the computing device to one or more other computing devices in the computing fabric. The one or more other computing devices individually contain a copy of the state information associated with the software application.

Abstract: Various techniques for distributed storage of state information in a computing fabric are disclosed herein. In one embodiment, a method includes executing a software application at a computing device of a computing fabric, and thus resulting in a change to a portion of a copy of state information associated with the software application stored in the computing device. The method also includes automatically replicating the change to the portion of the copy of state information stored on the computing device to one or more other computing devices in the computing fabric. The one or more other computing devices individually contain a copy of the state information associated with the software application.

Abstract: A multi-version removal manager for a transaction processing system is disclosed. A visibility sequence number is provided to versions such that operations with a lower sequence number than the visibility sequence number have been applied and a preselected amount of operations with a higher sequence number could have been applied. Visible version versions are maintained and versions related to a visibility sequence number are removed after an executing transaction is disposed.

Abstract: A transactional replicator applying group commit and barrier concepts is disclosed. Group commit means that the transactional replicator commits multiple transactions in a group and is not restricted to committing single transactions one-at-a-time and is not limited to operating on a single state provider. Barrier means that the transactional replicator does not move forward to commit additional transactions until the previous group of transactions are completed. All state providers must apply their transactions and update state before additional transactions will be committed. A quorum acknowledgement “unlocks” any locks that were acquired to update the state within a state provider. However, as long as there are no lock conflicts, additional transactions can continue to create new group commits as necessary.

Abstract: Various techniques for distributed storage of state information in a computing fabric are disclosed herein. In one embodiment, a method includes executing a software application at a computing device of a computing fabric, and thus resulting in a change to a portion of a copy of state information associated with the software application stored in the computing device. The method also includes automatically replicating the change to the portion of the copy of state information stored on the computing device to one or more other computing devices in the computing fabric. The one or more other computing devices individually contain a copy of the state information associated with the software application.