18223824. DATABASE-NATIVE AUTOMATIC COMPENSATION FOR SAGAS simplified abstract (Oracle International Corporation)

From WikiPatents
Jump to navigation Jump to search

DATABASE-NATIVE AUTOMATIC COMPENSATION FOR SAGAS

Organization Name

Oracle International Corporation

Inventor(s)

VASUDHA Krishnaswamy of Fremont CA (US)

DIETER Gawlick of Palo Alto CA (US)

MAHESH BABURAO Girkar of Los Altos CA (US)

AMIT Ketkar of Redwood City CA (US)

JIAQI Wang of Redwood City CA (US)

PAVAS Navaney of Redwood City CA (US)

DATABASE-NATIVE AUTOMATIC COMPENSATION FOR SAGAS - A simplified explanation of the abstract

This abstract first appeared for US patent application 18223824 titled 'DATABASE-NATIVE AUTOMATIC COMPENSATION FOR SAGAS

Simplified Explanation

The abstract describes a database-native Lock-Free Reservation infrastructure that automatically compensates for updates made by successful local transactions that are part of a saga being aborted.

  • The infrastructure tracks reservable column updates in a reservations journal within the database.
  • The information is retained beyond the commit of the local transaction until the finalization of the saga.
  • If the saga aborts, the database server uses the reservations journal to compensate for changes made by committed transactions in the saga.

Potential Applications

This technology could be applied in distributed systems, financial transactions, and e-commerce platforms.

Problems Solved

1. Automatic compensation for aborted transactions in a distributed system. 2. Ensuring data consistency and integrity in a saga-based architecture.

Benefits

1. Improved reliability and fault tolerance in distributed systems. 2. Simplified management of compensating transactions. 3. Enhanced data consistency across multiple transactions.

Potential Commercial Applications

Optimizing transaction processing in financial institutions.

Possible Prior Art

There may be prior art related to compensating transactions in distributed systems, but specific examples are not provided in the abstract.

Unanswered Questions

How does the infrastructure handle concurrent updates to the same reservable column?

The abstract does not mention how conflicts between concurrent updates are resolved within the reservations journal.

What is the performance impact of using the reservations journal on database operations?

The abstract does not address the potential overhead or latency introduced by tracking reservable column updates in the database.


Original Abstract Submitted

A database-native Lock-Free Reservation infrastructure is used to provide automatic compensation for the reservable column updates made by successful local transactions (or microservice actions) that are part of a saga that is being aborted. The automatic compensation is achieved by tracking the reservable column updates in a reservations journal, within the database, during the execution of the local transaction and remembering them beyond the commit of the local transaction until the finalization of the saga that the transaction is a part of. If the saga aborts, then the database server automatically uses the information retained in the reservations journal to compensate for the changes made by the committed transactions that were part of the saga.