Event Stream Data Synchronization Across Platforms

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques for managing data across different technology platforms often result in inadequate data synchronization, leading to disruptions and diminished user experience due to independent data updates across platforms.

Innovation Solution

A method and system for synchronizing data across multiple platforms by retrieving change events, parsing records, and updating databases using a synchronization database, which includes generating service tickets and event messages to facilitate data migration and reconciliation, while managing latency and error conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional techniques are used to manage data across different technology platforms, then each platform can operate independently, but data synchronization becomes inadequate leading to disruptions and diminished user experience

Engineering Contradiction:
Improvedata synchronization accuracyVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an event stream as an intermediary mechanism between different technology platforms. This event stream captures data change events from source platforms and delivers them to target platforms, ensuring reliable data synchronization without requiring direct platform-to-platform communication. The event stream acts as a mediator that resolves the contradiction by maintaining data accuracy while enabling independent platform operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms through event streams that track and communicate data change events between platforms. By continuously monitoring data changes and propagating updates through the event stream, the system ensures that all platforms maintain synchronized data states, thereby improving reliability without compromising ease of operation.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If data updates occur independently in each technology platform, then platform autonomy is maintained, but synchronization challenges arise requiring complex management tools

Engineering Contradiction:
Improveplatform independenceVSAvoidsynchronization management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the synchronization management function from the platform infrastructure itself and relocates it to an external event stream mechanism. This allows platforms to maintain their autonomy and independence while the event stream handles all synchronization operations externally, reducing the complexity burden on individual platforms while preserving platform versatility.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If data is synchronized across multiple platforms, then data consistency is improved, but latency and error conditions may occur during data migration

Engineering Contradiction:
Improvedata consistencyVSAvoiddata migration latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-configuring event streams and establishing data change event capture mechanisms before data migration begins. This preliminary setup ensures that when data changes occur, they are immediately captured and propagated without delay, reducing migration latency while maintaining data consistency across platforms.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11809452B2Method and system for data synchronization
Publication Date: 2023.11.07 JPMORGAN CHASE BANK NA
  • US11809452B2 patent drawing
  • US11809452B2 patent drawing
  • US11809452B2 patent drawing

AI summary

A method for facilitating data synchronization across a plurality of platforms is provided. The method includes retrieving a change event, the change event corresponding to an event stream from a first platform; parsing the change event to identify a record and a data operation; examining a synchronization database to determine whether a corresponding record is persisted in a database of a second platform; inserting the record into the synchronization database when the corresponding record is not persisted in the platform, the inserted record including a change indicator; and updating, by using the synchronization database, the database of the second platform to include the record.