Cloud Transaction Routing With Replica Redo-Log Reads
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing relational database management systems, the master node is easily overloaded, and load balancing is poor during transaction distribution.
Innovation Solution
A cloud service-based transaction processing method where a target replica node processes redo logs to generate modification records, shares load pressure with the master node by reading data based on these records, and improves load balancing by distributing read and write operations across different nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the proxy node sends both read and write operations to the master node, then data consistency is ensured, but the master node becomes overloaded and load balancing deteriorates
Solution Approach 1:
The patent segments transaction operations into read operations and write operations, routing them to different nodes. Read operations are sent to replica nodes while write operations are sent to the master node, dividing the workload to prevent master node overload while maintaining data consistency through the replica-based architecture.
Solution Approach 2:
The proxy node acts as an intermediary that receives transaction processing requests, determines the operation type, and routes them appropriately. It sends read operations to replica nodes and write operations to the master node, mediating the distribution of operations to balance load while ensuring consistency.
2Productivity
If the proxy node sends read operations to replica nodes, then load balancing improves, but data consistency may be compromised
Solution Approach 1:
The patent uses replica nodes that copy data from the master node to distribute read operations. Multiple replica nodes maintain copies of the data, allowing read operations to be served from these copies while the master node handles only write operations, thus improving load balancing while maintaining consistency through the replication mechanism.
3Reliability
If the master node processes all write operations, then data consistency is maintained, but the master node is easily overloaded
Solution Approach 1:
The patent segments the processing load by separating write operations (handled by master node) from read operations (handled by replica nodes). This segmentation reduces the processing burden on the master node while maintaining data consistency, as only write operations need to be processed centrally to ensure consistency.
Data Source
AI summary
A cloud service-based transaction processing method includes that when receiving a transaction processing request that includes both a read operation and a write operation, a proxy node sends the write operation to a master node, and sends the read operation to a replica node. The replica node synchronizes a redo log generated based on the write operation, and further, may read data corresponding to the write operation by using a modification record generated during processing of the redo log. In this way, the master node does not need to process the read operation.