Cloud Synchronization Engine for Multi-Platform Data Conflict Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud-based application platforms face inefficiencies in synchronizing data between multiple platforms, leading to underutilization of application data due to the high computational resources required for peer-to-peer synchronization techniques.
Innovation Solution
A synchronization engine is introduced as a centralized point for synchronizing application data between multiple platforms, using object and function mappings to resolve conflicts and apply machine learning functions, thereby reducing the need for direct API calls between platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If peer-to-peer synchronization techniques are used between application platforms, then data synchronization capability is provided, but computational resources and API calls increase significantly
Solution Approach 1:
A cloud-based synchronization service is introduced as an intermediary between application platforms. Instead of platforms directly synchronizing with each other through peer-to-peer API calls, all synchronization operations are routed through this centralized cloud service, which manages the communication overhead and computational resources required for data synchronization.
Solution Approach 2:
The synchronization service provides universal synchronization capability across multiple application platforms. A single cloud-based service handles synchronization for various platforms (e.g., CRM, marketing automation, support systems), eliminating the need for each platform to implement its own synchronization logic and reducing redundant API calls.
2Reliability
If peer-to-peer synchronization techniques are used between application platforms, then data synchronization capability is provided, but the number of API calls increases significantly
Solution Approach 1:
The cloud-based synchronization service acts as a mediator that consolidates multiple API calls. Rather than Platform A making direct API calls to Platform B and C, the synchronization service receives data from all platforms and manages the propagation, significantly reducing the total number of API calls required.
Solution Approach 2:
The synchronization architecture is segmented into three distinct components: data sources (application platforms), the synchronization service (cloud-based intermediary), and data destinations (other platforms). This segmentation allows the service to buffer and manage API calls efficiently, reducing direct platform-to-platform communication overhead.
3Use of energy by moving object
If centralized synchronization service is introduced, then computational resources are reduced, but system architecture complexity increases
Solution Approach 1:
While the architecture does become more complex with the introduction of a centralized service, the service itself is designed as a relatively simple intermediary that handles synchronization through standardized protocols. The complexity is centralized in one location rather than distributed across all platforms, making the overall system more manageable.
Data Source
AI summary
In embodiments, application data is received from multiple application platforms. Once received, an object mapping is used to determine a synchronization data object that is mapped to data objects from the application data. A function mapping is used to determine one or more functions to apply to the application data. Data objects from the application data that are mapped to the synchronization data object are compared to detect conflicts between fields. In response to detecting a conflict, the conflict is resolved based on configuration rules that indicate priority between fields of different data objects. Once the conflict is resolved, the data objects are merged into a modified synchronization data object that represents an updated version of the synchronization data object. Changes between the synchronization data object and the modified synchronization data object are identified and propagated to application platforms to perform updates to application data managed by the application platforms.