System with multiple conditional commit databases

1. A system for processing a transaction, comprising:

a processor configured to:

check a condition using data in a first database as part of processing a first prepare, wherein the data is associated with a transaction, wherein the data in the first database is latched before checking the condition and is unlatched after checking the condition;

indicate to a second database to check the same condition using data in the second database as part of a second prepare, wherein the data is associated with the transaction, wherein the data in the second database is latched before checking the condition and is unlatched after checking the condition;

determine whether the condition check in the first database and the second database has passed;

in the event both condition checks have passed, implement a commit state associated with the transaction in the first database, wherein the data in the first database is latched before implementing the commit state in the first database and is unlatched after the implementing of the commit state in the first database;

indicate to the second database that the commit state is to be implemented in the second database, wherein the data in the second database is latched before implementing the commit state in the second database and is unlatched after the implementing of the commit state in the second database; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system as in claim 1 , wherein the processor is further configured to receive an indication from the second database that the condition check was satisfied using data in the second database.

3. The system as in claim 1 , wherein the condition check using data in a first database is part of implementing a prepare locally.

4. The system as in claim 1 , wherein the condition check using data in the second database is part of implementing a prepare non-locally.

5. The system as in claim 1 , wherein the processor is further configured to determine whether to proceed with processing the transaction based at least in part on the condition check in the first database and the second database.

6. The system as in claim 5 , wherein in the event that the condition is satisfied, a transaction buffer is allocated.

7. The system as in claim 6 , where in the transaction buffer comprises a transaction condition list.

8. The system as in claim 6 , where in the transaction buffer comprises a transaction command.

9. The system as in claim 5 , wherein in the event that the condition is valid, an update buffer is created or allocated.

10. The system as in claim 9 , wherein the update buffer comprises a maximum value.

11. The system as in claim 9 , wherein the update buffer comprises a minimum value.

12. The system as in claim 9 , wherein the update buffer comprises a number of transactions.

13. The system as in claim 1 , wherein implementing a commit state comprises updating a data.

14. The system as in claim 1 , wherein implementing a commit state comprises updating an update buffer.

15. The system as in claim 1 , wherein implementing a commit state comprises updating a transaction buffer.

16. A method for processing a transaction, comprising:

checking a condition using data in a first database as part of processing a first prepare, wherein the data is associated with a transaction, wherein the data in the first database is latched before checking the condition and is unlatched after checking the condition;

indicating to a second database to check the same condition using data in the second database as part of a second prepare, wherein the data is associated with the transaction, wherein the data in the second database is latched before checking the condition and is unlatched after checking the condition;

determining whether the condition check in the first database and the second database has passed;

in the event both condition checks have passed, implementing a commit state associated with the transaction in the first database, wherein the data in the first database is latched before implementing the commit state in the first database and is unlatched after the implementing of the commit state in the first database; and

indicating to the second database that the commit state is to be implemented in the second database, wherein the data in the second database is latched before implementing the commit state in the second database and is unlatched after the implementing of the commit state in the second database.

17. A computer program product for processing a transaction, the computer program product comprising a non-transitory computer readable storage medium storing computer instructions for:

checking a condition using data in a first database as part of processing a first prepare, wherein the data is associated with a transaction, wherein the data in the first database is latched before checking the condition and is unlatched after checking the condition;

indicating to a second database to check the same condition using data in the second database as part of a second prepare, wherein the data is associated with the transaction, wherein the data in the second database is latched before checking the condition and is unlatched after checking the condition;

determining whether the condition check in the first database and the second database has passed;

in the event both condition checks have passed, implementing a commit state associated with the transaction in the first database, wherein the data in the first database is latched before implementing the commit state in the first database and is unlatched after the implementing of the commit state in the first database; and

indicating to the second database that the commit state is to be implemented in the second database, wherein the data in the second database is latched before implementing the commit state in the second database and is unlatched after the implementing of the commit state in the second database.