Local Database Synchronization During Intermittent Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for client terminals accessing data stored on remote servers face disruptions during communication outages, leading to productivity loss and data loss, as they lack centralized data storage and synchronization capabilities, resulting in segmented, non-centralized, and non-portable data access.
Innovation Solution
A local communication device that stores data from multiple sources, including remote and local servers, and client terminal devices, converts data to a predefined format, and synchronizes databases, providing access during outages and re-establishing connections when network access is restored, using a software agent, storage module, conversion module, and synchronizing module.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If client terminals access data stored on remote servers, then data accessibility is improved, but system reliability deteriorates during communication outages
Solution Approach 1:
The system performs preliminary actions by caching data from remote servers to local storage before communication outages occur. The offline mode capability is prepared in advance, allowing clients to access previously cached data when network connectivity is unavailable, thus maintaining system reliability during outages while preserving data accessibility.
Solution Approach 2:
The system introduces a local cache/storage intermediary between the client terminal and remote server. This intermediary layer stores data locally, allowing clients to access data without direct server connectivity. The cache acts as a mediator that maintains the data access function even when the primary remote storage path is unavailable during communication outages.
2Reliability
If data is stored in separate databases for each application, then data security is improved, but data sharing deteriorates
Solution Approach 1:
The system implements a universal data storage architecture where a single offline database on the client terminal serves multiple applications simultaneously. This multi-functional database can be accessed by different applications running on the client, enabling data sharing while maintaining security through controlled access. The same storage infrastructure supports both secure isolation and collaborative access needs.
Solution Approach 2:
The system merges multiple application-specific data storage requirements into a single unified offline database on the client terminal. Instead of maintaining separate physical databases for each application, the system combines them into one shared storage resource that can be securely accessed by multiple applications, thus improving data sharing while preserving security through access control mechanisms.
3Ease of operation
If multiple applications store data locally on client terminals, then offline access is improved, but system complexity deteriorates
Solution Approach 1:
The system employs a universal offline database that serves all applications on the client terminal simultaneously. This single multi-functional storage solution replaces the need for multiple separate local databases, thereby maintaining offline access capability for all applications while reducing overall system complexity by eliminating redundant storage infrastructure.
Data Source
AI summary
A method and database server for synchronizing contents of a local database with contents of a remote database. The method includes writing data transactions to a local transaction log file, assigning bin numbers to the data transactions, and determining if the assigned bin numbers have changed due to receipt of subsequent data transactions and if the bin numbers have changed, inserting the subsequent data transactions into a local sequence log file and assigning the subsequent data transactions a first sequence number. The method includes providing, to a remote replicator service, access to the first sequence number, the remote replicator service having access to a second sequence number, and if the first sequence number does not match the second sequence number, providing to the remote replicator service access to the subsequent data transactions, the remote replication service updating a remote database to include the subsequent data transactions.