Global database transaction management service

A system comprising:

• a plurality of data engines each storing or otherwise making data available to remote client computing systems, at least a portion of the data engines being heterogeneous, each data engine comprising at least one programmable data processor and memory,
• a transaction broker server and a lock manager server forming a transaction management service layer;
• wherein the transaction management service layer:
• monitors, via client libraries at each of the plurality of data engines, a plurality of read and write transactions being executed by the data engines;
• maintains and coordinates transaction timestamp and sequence numbers that are shared by the plurality of data engines;
• identifies conflicts among the plurality of transactions;
• resolves the identified conflicts among the plurality of transactions using optimistic concurrency control, hybrid locking such that database transactions are committed prior to corresponding lock requests being granted and such transactions are rolled back if such lock requests are not granted;
• and
• is a separate and independent service that is isolated from other components of the plurality of data engines to provide a single transaction domain across the heterogeneous data engines;
• wherein the transaction broker server provides a minimum snapshot timestamp which is used to determine which data across all of the data engines is to be subject to garbage collection.

A non-transitory computer program product storing instructions which, when executed by at least one data processor forming part of at least one computing device, perform operations comprising:

• monitoring, by a transaction management service layer executed by a transaction broker server and a lock manager server and via client libraries at each of a plurality of data engines, a plurality of read and write transactions being executed by the data engines, at least a portion of the data engines being heterogeneous;
• maintaining and coordinating, by the transaction management service layer, transaction timestamp and sequence numbers that are shared by the plurality of data engines;
• identifying, by the transaction management service layer, conflicts among the plurality of transactions;
• and
• resolving, by the transaction management service layer, the identified conflicts among the plurality of transactions;
• wherein:
• the transaction management service layer is a separate and independent service that is isolated from other components of the plurality of data engines;
• each data engine comprises a different client library embedded therein that wraps access methods associated with both of a transaction broker server and a lock manager server that together execute the transaction management service layer;
• the transaction broker server maintaining a global commit timestamp which is incremented when a global write transaction commits across one or more of the data engines;
• the lock manager resolves conflicts using a hybrid of optimistic locking and pessimistic locking such that database transactions are committed prior to corresponding lock requests being granted and such transactions are rolled back if such lock requests are not granted;
• and
• the transaction broker server provides a minimum snapshot timestamp which is used to determine which data across all of the data engines is to be subject to garbage collection.