Transaction Synchronization Function for Heterogeneous Closed Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Closed systems, which rely on third-party database management systems for data management, pose challenges in data synchronization across different vendor systems, as they often lack direct access to the underlying DBMS and require modifications that may not be feasible or timely.
Innovation Solution
A transaction synchronization function that converts user transactions into a common format, allowing them to be submitted through vendor interfaces to respective databases within closed systems, enabling synchronization without modifying the systems or accessing the underlying DBMS, using a process that involves storing transactions in synchronization files and translating them for submission to different vendor interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If direct access to underlying DBMS is implemented, then data synchronization capability is improved, but system complexity and vendor interface constraints worsen
Solution Approach 1:
The patent introduces a synchronization layer as an intermediary component that sits between multiple closed systems and their respective DBMS instances. This synchronization layer captures data change events from one system and propagates them to other systems through standardized interfaces, enabling data synchronization without requiring direct access to underlying DBMS or modifying the closed systems themselves.
2Adaptability or versatility
If modifications to closed systems are made, then synchronization functionality is improved, but ease of operation and implementation feasibility worsen
Solution Approach 1:
The patent segments the synchronization functionality into a separate, independent component (the synchronization layer) that does not require modification of the closed systems. This segmentation allows the synchronization capability to be implemented and maintained independently, preserving the integrity and operational simplicity of the original closed systems while adding the desired synchronization functionality.
3Reliability
If vendor-specific native database interfaces are used, then system reliability is improved, but adaptability across different vendors worsens
Solution Approach 1:
The patent creates a universal synchronization layer that can work with multiple different vendor-specific closed systems through their respective standardized interfaces. This synchronization layer implements a vendor-agnostic event capture and propagation mechanism that translates between different vendor interfaces and a common synchronization protocol, enabling cross-vendor data synchronization while maintaining the reliability of each vendor's native interface.
Data Source
AI summary
Methods, systems, and computer program products for synchronizing a first closed system with a second closed system are disclosed. A first transaction synchronization function on a first computing device receives a first plurality of user transactions and stores corresponding transaction records in a first synchronization file in a common format. The first transaction synchronization function submits the first plurality of user transactions to the first closed system via a first vendor interface for application to a first database. A second computing device accesses the first synchronization file, translates the transaction records in accordance with a second vendor interface, and submits the translated transaction records to a second closed system via a second vendor interface for application to a second closed system.