Database Integration System Using Link Transactions
Solution Overview
Problem
Current database integration systems require complex middleware to enable communication between diverse databases, leading to inefficiencies and data inconsistencies across systems, especially in scenarios where databases have different structures and are used by different users in real-time.
Innovation Solution
A database integration system that integrates databases at the data layer, using a mapping process to generate routed transactions from link transactions, allowing for synchronization without the need for middleware applications, and utilizing update queues for handling transactions even when systems are offline, with priority ordering and timestamp management to ensure data consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If middleware is used to enable communication between diverse databases, then database integration is achieved, but system complexity increases and data inconsistencies occur
Solution Approach 1:
The patent extracts the integration logic from the application layer and places it directly at the database layer. Each database system independently generates link transactions that are routed to target databases without requiring external middleware, thereby eliminating the complexity of middleware-based integration while maintaining database integration capability
Solution Approach 2:
The database systems perform integration operations autonomously by generating and routing their own link transactions. Each database acts as both a source and target of integration operations, eliminating the need for centralized middleware management and reducing overall system complexity
2Reliability
If middleware is used to synchronize databases, then data synchronization is achieved, but real-time processing efficiency decreases
Solution Approach 1:
The patent segments the transaction processing into root transactions at the application layer and link transactions at the database layer. This segmentation allows real-time processing of root transactions while link transactions are asynchronously routed and applied to target databases, maintaining data consistency without blocking real-time operations
Solution Approach 2:
The system performs preliminary actions by generating link transactions immediately when root transactions are executed. These link transactions are prepared and queued for routing before actual data synchronization occurs, enabling real-time processing continuity while ensuring data consistency through pre-prepared synchronization operations
3Reliability
If database locking is used to ensure data consistency, then data integrity is maintained, but transaction processing speed decreases
Solution Approach 1:
The patent introduces link transactions as intermediaries between root transactions and data synchronization operations. These link transactions carry the necessary information to replicate data changes without requiring locking mechanisms, maintaining data integrity through asynchronous replication rather than concurrent control
Solution Approach 2:
The system maintains continuous transaction processing by decoupling the execution of root transactions from the application of link transactions. Data integrity is maintained through the continuous generation and routing of link transactions, eliminating the need to pause or lock databases during transaction processing
4Adaptability or versatility
If diverse database structures are integrated, then system versatility is improved, but mapping and synchronization complexity increases
Solution Approach 1:
The patent creates a universal link transaction format that can represent data changes across diverse database structures. This standardized format enables different database types and structures to be integrated without requiring complex pairwise mapping configurations, as the link transaction structure adapts to various database schemas through a common interface
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The invention provides for a method of using a database assembly (100). The database assembly comprises at least three computing systems (102, 104, 106). Each of the at least three computing systems comprises at least one application (116) and a local database system (118).The database assembly further comprise a database integration system (108) and a network connection (110) between each of the at least three computing systems and the database integration system. The method comprises: receiving (200) a first root transaction (130) by the local database of a first computing system (102); executing (202) the first root transaction on the local database of the first computing system; generating (204) a first link transaction (132) by the local database of the first computing system; sending (206) the first link transaction from the first computing system to the database integration system via the network connection of the first computing system; generating (208) a first routed transaction (134, 136) for at least one of the first remaining computing systems (104, 106) by the data base integration system; sending (210) the first routed transaction to the at least one of the remaining computing systems via the network connection; and executing (212) the first routed transaction on the local database of the at least one of the remaining computer system.