Interdependent Data Object Migration via Dependency Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

During the migration of data from legacy applications to new target applications, changes are not always applied in the same order due to data and API restrictions, leading to issues with interdependent data objects.

Innovation Solution

A system and method for migrating interdependent data objects involve determining the dependencies between data objects, caching the first data object until the required second data object is available, and automatically sending both objects to the target device upon receipt of the second data object, ensuring that interdependencies are met.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data objects are migrated in the order they are received from the legacy application, then the migration process is simple and fast, but the target application may receive data in an incorrect sequence that violates its data dependencies and API restrictions

Engineering Contradiction:
Improvemigration speedVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary analysis of data object dependencies before migration begins. It identifies which data objects must be migrated together or in specific sequences based on the target application's requirements. This preliminary action allows the system to prepare migration batches in advance, ensuring that when migration occurs, the correct sequencing is already determined, thus maintaining both speed and integrity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The migration process is segmented into multiple batches or groups based on data object dependencies. Instead of migrating all data objects in a single sequential pass, the system divides them into segments that can be migrated in parallel or in specific sequences. Each segment is independently managed, allowing the system to optimize the migration of each segment while ensuring overall data integrity across all segments.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the system waits for all dependent data objects before migrating any single object, then data integrity is maintained, but the migration process becomes significantly slower and less efficient

Engineering Contradiction:
Improvedata integrityVSAvoidmigration speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The migration system dynamically adjusts the sequencing and batching of data objects based on real-time analysis of dependencies. Rather than following a static predetermined sequence, the system continuously evaluates which data objects are ready to be migrated and which must wait for their dependencies. This dynamic approach allows the system to migrate data as soon as dependencies are satisfied, maximizing throughput while maintaining integrity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms that continuously monitor the migration progress and dependency satisfaction status. When a data object's dependencies are fulfilled, the system immediately triggers its migration. This feedback loop ensures that no data object is migrated before its dependencies are ready, maintaining integrity, while also ensuring that migration occurs as soon as possible, maximizing productivity.

Inventive Principle:
Principle #23Feedback

3Reliability

If the system re-sequences all data objects to perfectly match the target system's requirements, then data integrity is ensured, but the complexity of the migration process increases significantly

Engineering Contradiction:
Improvedata integrityVSAvoidmigration process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system changes the parameter of data object sequencing from a fixed legacy order to a flexible target-order based on dependency analysis. By parameterizing the sequencing logic to adapt to the target application's specific requirements, the system can automatically determine the correct migration sequence without hardcoding complex re-sequencing rules. This parameter-based approach reduces complexity while ensuring integrity.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system introduces an intermediary layer or translation service that sits between the legacy application and the target application. This intermediary analyzes the data objects, determines their correct sequencing based on target requirements, and manages the migration process. By offloading the complex re-sequencing logic to this intermediary component, the overall migration process becomes more manageable and less complex, while still ensuring data integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9665602B1System, method, and computer program for migrating interdependent data objects from a first device to a second device
Publication Date: 2017.05.30 AMDOCS DEV LTD
  • US9665602B1 patent drawing
  • US9665602B1 patent drawing
  • US9665602B1 patent drawing

AI summary

A system, method, and computer program product are provided for migrating interdependent data objects from a first device to a second device. In use, at least one first data object to be migrated from a first device to a second device associated with a target code is received. Further, it is determined that the second device associated with the target code requires at least one second data object to be present at least one of before the at least one first data object or at a same time as the at least one first data object. Additionally, the at least one first data object to be migrated from the first device to the second device associated with the target code is stored in a cache. Furthermore, an interdependency event associated with the at least one first data object and the at least one second data object is detected. In response to detecting the interdependency event, the at least one second data object to be migrated from the first device to the second device associated with the target code is received. Moreover, the at least one first data object and the at least one second data object are automatically sent to the second device associated with the target code, in response to receiving the at least one second data object.