Event Object Encapsulation for Remote Database Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional database synchronization technologies experience high delays and inefficiencies, particularly over long distances, leading to data collisions and inconsistencies between remote databases.
Innovation Solution
A computer-implemented method where service data updates are encapsulated into event objects, transmitted in real-time between peer-end service applications, focusing on the final status or event version rather than intermediate processes, to ensure rapid and reliable data synchronization without unnecessary network traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional database synchronization technologies are used over long distances, then data can be synchronized between remote databases, but synchronization delay increases and synchronization efficiency decreases
Solution Approach 1:
The system performs preliminary actions by capturing data change events locally with version timestamps before transmission. Each data change is recorded with its occurrence time, allowing the receiving database to determine synchronization order based on these pre-captured timestamps rather than relying on transmission timing, thus resolving the synchronization delay issue in long-distance scenarios
Solution Approach 2:
The patent creates simplified copies of data change events in the form of version records that contain only essential information (change type, version timestamp, data identifier). These lightweight copies are transmitted instead of full data sets or complex transaction logs, reducing transmission time and improving synchronization efficiency while maintaining data consistency
2Reliability
If traditional database synchronization technologies are used, then data can be synchronized between databases, but data collision occurs and data inconsistency increases
Solution Approach 1:
The system implements feedback mechanisms where each database sends data change events with version timestamps to the other database. The receiving database compares these version timestamps with its local versions to determine whether to apply changes. This feedback loop ensures that only valid, non-conflicting changes are applied, preventing data collisions and maintaining consistency
Solution Approach 2:
The patent introduces version timestamps as a new parameter to track data changes. By comparing version timestamps rather than attempting to lock or coordinate complex transactions, the system simplifies conflict detection and resolution. Changes are applied based on version ordering, which eliminates data collisions caused by simultaneous updates
3Loss of information
If intermediate processes and database instructions are transmitted frequently, then detailed synchronization information is maintained, but transmission traffic increases and network resource utilization decreases
Solution Approach 1:
The system extracts only the essential elements of data changes—specifically the version timestamp, change type, and data identifier—into compact event records. Intermediate processing steps, full data payloads, and complex SQL instructions are excluded. This extraction approach maintains sufficient synchronization information for conflict resolution while dramatically reducing transmission traffic and improving network resource utilization
Data Source
AI summary
Service data updated in a data update event is acquired by a service application executed by a computer-implemented system. The service data is stored in a local database of the service application. An event version corresponding to the data update event is generated by the service application. The service data and the event version are encapsulated into an event object by the service application. The event object is transmitted to a peer-end service application for synchronizing corresponding service data in a peer-end database of the peer-end service application.