Mobile Database Synchronization via Segmented Change Sets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices face inefficiencies in synchronizing with central databases due to memory and network limitations, and the need to handle diverse operating systems and software frameworks.
Innovation Solution
A method and system for synchronizing a local database with a remote database, involving defining service operations, processing transactions, capturing operation calls, and change sets, with modules to support different business logic and target platforms, enabling efficient data exchange and synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If mobile devices maintain local copies of database data for offline access, then accessibility and ease of operation are improved, but data consistency and reliability with the central database deteriorate due to intermittent or unreliable network connections
Solution Approach 1:
The synchronization process is segmented into discrete operations: capturing local changes, transmitting to server, and applying remote changes. This segmentation allows the system to handle network interruptions between segments without compromising overall reliability, while maintaining local accessibility during each segment's execution.
Solution Approach 2:
The system performs preliminary actions by capturing local database changes before network transmission is needed. Change sets are prepared and queued in advance, allowing the mobile device to maintain operational capability while ensuring data consistency is restored once network connectivity is established.
2Reliability
If the system captures and processes all transaction operations for synchronization, then data consistency between local and remote databases is improved, but processing time and device resource consumption increase
Solution Approach 1:
The system extracts only the essential information needed for synchronization - operation calls and change sets - from the full transaction processing. By taking out only these critical elements for capture and transmission, the system maintains data consistency while minimizing processing time and resource consumption on the mobile device.
Solution Approach 2:
The system applies partial action by capturing and processing only the necessary transaction operations for synchronization purposes, rather than processing every possible operation. This selective approach ensures data consistency is maintained for relevant data while reducing unnecessary processing time and resource usage.
3Adaptability or versatility
If the synchronization system is designed to work across multiple operating systems and software frameworks, then adaptability and versatility are improved, but system complexity increases
Solution Approach 1:
The synchronization system is designed with universal components that can operate across multiple operating systems and software frameworks. The core synchronization mechanism uses platform-independent concepts such as change sets and operation calls, allowing the same system to function on different platforms without increasing overall complexity.
Solution Approach 2:
The system introduces an intermediary layer between the mobile device and central database that abstracts platform-specific details. This intermediary handles the complexity of different operating systems and software frameworks, allowing the core synchronization logic to remain simple while maintaining broad adaptability.
Data Source
AI summary
A system, method, and computer program product are provided for synchronizing a local database with a remote database. Additionally, a system, method, and computer program product are provided for performing a service operation on a database, the database located on a database system.