Back-End Storage Transaction Replication via Interceptor
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current e-commerce transaction replication systems are inefficient due to the need for specific replication managers and receivers tied to particular database systems, leading to inconvenience and inefficiency when switching between different database systems, and they often burden front-end host resources.
Innovation Solution
Implementing a back-end e-commerce transaction replication method where a second data storage system determines whether to commit a transaction based on parsed information compared to predetermined criteria, using an interceptor device to perform replication and translation functions without requiring corresponding pairs of replication managers and receivers, thus minimizing host resource burden and allowing for real-time, intelligent transaction processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If front-end replication managers and receivers are used for transaction replication, then transaction replication can be achieved, but host resource burden increases and system complexity increases
Solution Approach 1:
The patent extracts the replication function from the front-end host and relocates it to the back-end storage system. The storage system directly receives transactions from the front-end host and performs replication without requiring corresponding replication managers and receivers on the host, thereby reducing host complexity while maintaining replication capability
Solution Approach 2:
The storage system acts as an intermediary between the front-end host and the replication target. It receives transactions, parses them, determines commitment based on criteria, and performs replication, eliminating the need for host-based replication software pairs
2Reliability
If specific replication managers and receivers tied to database systems are used, then transaction replication works for that database, but adaptability to database system changes deteriorates
Solution Approach 1:
The storage system provides universal replication capability that is not tied to specific database systems. It receives transactions in various formats, parses them, and performs replication based on predetermined criteria, making it adaptable to different database systems without requiring database-specific replication software
Solution Approach 2:
The system creates a generic copy of the replication function that can work with multiple database systems. Instead of having database-specific replication managers, the storage system maintains a universal replication mechanism that can handle different transaction formats and database systems through standardized interfaces
3Reliability
If batch mode transaction replication is used, then replication can be achieved, but real-time processing capability deteriorates
Solution Approach 1:
The storage system performs preliminary parsing and commitment determination of transactions before replication. By preparing transaction information in advance and making real-time commitment decisions based on parsed data, the system enables real-time replication without requiring batch processing
Data Source
AI summary
The back-end data storage system of an e-commerce system receives a replicated transaction from the data storage system of another e-commerce system and makes a determination or decision whether to commit the replicated transaction based upon a comparison of information parsed from the transaction with predetermined commit criteria.