Database Integration System Using Routed Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database integration methods require complex middleware and are not scalable for real-time transaction processing across diverse database systems, leading to data inconsistencies and increased operational costs due to the need for constant system availability.
Innovation Solution
A database integration system that integrates databases at the data layer, using a mapping process to generate routed transactions across multiple systems, with an update queue for handling transactions even when systems are offline, and prioritizing critical transactions based on timestamps and user permissions, eliminating the need for database locking and middleware applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If middleware is used to integrate databases, then data synchronization between systems is achieved, but system complexity and operational costs increase
Solution Approach 1:
The patent extracts the integration logic from complex middleware applications and embeds it directly into the database management system. The database engine now natively supports distributed transaction processing, link transactions, and routed transactions, eliminating the need for external middleware to handle data synchronization between diverse database systems.
Solution Approach 2:
The database management system is enhanced with universal transaction processing capabilities that work across multiple diverse database systems. The system can generate and process root transactions, link transactions, and routed transactions universally, allowing a single database system to integrate with various other database types without requiring different middleware for each integration scenario.
2Reliability
If middleware applications are deployed for database integration, then data consistency is maintained, but system availability requirements increase operational costs
Solution Approach 1:
The database management system performs data consistency maintenance autonomously through built-in transaction processing mechanisms. When a root transaction modifies data, the system automatically generates link transactions and routed transactions to propagate changes to other databases, eliminating the need for continuous middleware monitoring and manual consistency checks that incur operational costs.
Solution Approach 2:
The system establishes transaction processing rules and data mapping configurations in advance through metadata definitions. This preliminary setup enables automatic transaction routing and data synchronization without requiring real-time middleware intervention, reducing ongoing operational costs while maintaining data consistency.
3Adaptability or versatility
If traditional middleware integration is used, then diverse database systems can communicate, but scalability for real-time processing is limited
Solution Approach 1:
The transaction processing architecture is segmented into distinct transaction types: root transactions initiated by applications, link transactions generated by the local database, and routed transactions sent to remote databases. This segmentation enables parallel processing of multiple transactions simultaneously, improving real-time processing capability while maintaining compatibility with diverse database systems through standardized transaction interfaces.
Solution Approach 2:
The patent introduces an intermediary transaction processing layer within the database management system that mediates between local database operations and remote database updates. This intermediary mechanism uses metadata-driven routing to automatically determine which databases need updates and propagates changes efficiently, enabling scalable real-time processing across diverse database systems without requiring complex point-to-point middleware connections.
Data Source
AI summary
The invention provides for a method of using a database assembly. The database assembly comprises at least three computing system. Each of the at least three computing systems comprises at least one application and a local database system. The database assembly further comprise a database integration system and a network connection between each of the at least three computing systems and the database integration system. The method comprises: receiving a first root transaction by the local database of a first computing system; executing the first root transaction on the local database of the first computing system; generating a first link transaction by the local database of the first computing system; sending the first link transaction from the first computing system to the database integration system via the network connection of the first computing system; generating a first routed transaction for at least one of the first remaining computing systems by the data base integration system; sending the first routed transaction to the at least one of the remaining computing systems via the network connection; and executing the first routed transaction on the local database of the at least one of the remaining computer system.