View source for Oracle international corporation (20240126781). CONSENSUS PROTOCOL FOR ASYNCHRONOUS DATABASE TRANSACTION REPLICATION WITH FAST, AUTOMATIC FAILOVER, ZERO DATA LOSS, STRONG CONSISTENCY, FULL SQL SUPPORT AND HORIZONTAL SCALABILITY simplified abstract

=CONSENSUS PROTOCOL FOR ASYNCHRONOUS DATABASE TRANSACTION REPLICATION WITH FAST, AUTOMATIC FAILOVER, ZERO DATA LOSS, STRONG CONSISTENCY, FULL SQL SUPPORT AND HORIZONTAL SCALABILITY=


==Organization Name==

[[:Category:oracle international corporation|oracle international corporation]]


[[Category:oracle international corporation]]

==Inventor(s)==

[[:Category:Lik Wong of Palo Alto CA (US)|Lik Wong of Palo Alto CA (US)]][[Category:Lik Wong of Palo Alto CA (US)]]

[[:Category:Leonid Novak of Castro Valley CA (US)|Leonid Novak of Castro Valley CA (US)]][[Category:Leonid Novak of Castro Valley CA (US)]]

[[:Category:Sampanna Salunke of San Carlos CA (US)|Sampanna Salunke of San Carlos CA (US)]][[Category:Sampanna Salunke of San Carlos CA (US)]]

[[:Category:Mark Dilman of Sunnyvale CA (US)|Mark Dilman of Sunnyvale CA (US)]][[Category:Mark Dilman of Sunnyvale CA (US)]]

[[:Category:Wei-Ming Hu of Palo Alto CA (US)|Wei-Ming Hu of Palo Alto CA (US)]][[Category:Wei-Ming Hu of Palo Alto CA (US)]]

==CONSENSUS PROTOCOL FOR ASYNCHRONOUS DATABASE TRANSACTION REPLICATION WITH FAST, AUTOMATIC FAILOVER, ZERO DATA LOSS, STRONG CONSISTENCY, FULL SQL SUPPORT AND HORIZONTAL SCALABILITY - A simplified explanation of the abstract==


This abstract first appeared for US patent application 20240126781 titled 'CONSENSUS PROTOCOL FOR ASYNCHRONOUS DATABASE TRANSACTION REPLICATION WITH FAST, AUTOMATIC FAILOVER, ZERO DATA LOSS, STRONG CONSISTENCY, FULL SQL SUPPORT AND HORIZONTAL SCALABILITY

==Simplified Explanation==

The abstract describes a consensus protocol-based replication approach where a leader server asynchronously executes database transactions, replicates change operations asynchronously, and replicates transaction commits synchronously.

* Leader server performs change operations on a copy of the database and creates replication log records.
* Leader server does not wait for consensus from followers for change operations.
* Leader server creates commit log records for commits and waits for consensus.
* Database transactions are executed asynchronously.
* Change operations are replicated asynchronously.
* Transaction commits are replicated synchronously.

== Potential Applications ==
The technology described in the patent application could be applied in:
* Distributed databases
* Cloud computing environments
* High-availability systems

== Problems Solved ==
This technology addresses issues such as:
* Ensuring consistency in replicated databases
* Improving fault tolerance in distributed systems
* Enhancing performance in cloud computing environments

== Benefits ==
The benefits of this technology include:
* Improved reliability and fault tolerance
* Increased performance and scalability
* Simplified management of distributed databases

== Potential Commercial Applications ==
A potential commercial application of this technology could be in:
* Enterprise database management systems

== Possible Prior Art ==
One possible prior art for this technology could be:
* Existing consensus protocols used in distributed systems

=== What are the specific consensus protocols used in this approach? ===

The abstract mentions a consensus protocol-based replication approach, but it does not specify which consensus protocols are utilized in the system. It would be beneficial to know the specific protocols employed for a better understanding of the technology.

=== How does this approach handle conflicts in replicated databases? ===

The abstract discusses asynchronous replication of change operations and synchronous replication of transaction commits but does not delve into how conflicts are managed in replicated databases. Understanding the conflict resolution mechanism would provide insights into the robustness of the system.


==Original Abstract Submitted==

a consensus protocol-based replication approach is provided. for each change operation performed by a leader server on a copy of the database, the leader server creates a replication log record and returns a result to the client. the leader does not wait for consensus for the change operation from the followers. for a commit, the leader creates a commit log record and waits for consensus. thus, the leader executes database transactions asynchronously, performs replication of change operations asynchronously, and performs replication of transaction commits synchronously.



[[Category:G06F16/27]]
[[Category:G06F16/22]]
[[Category:G06F16/23]]