Parallel Database Verification for Legacy Migration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The transition from a legacy database environment to a modern database environment is complex due to incompatible data architectures, making data validation difficult and inefficient, especially when replacing a legacy Pick environment with a modern microservice architecture.

Innovation Solution

Running parallel databases, with a database verification system comparing updates between the legacy and modern databases to ensure data integrity and consistency, allowing for gradual transition and fallback if necessary, while utilizing a database interface to synchronize updates across both systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a legacy database environment is replaced with a modern database environment, then data architecture modernization is achieved, but data validation becomes difficult and inefficient

Engineering Contradiction:

Improvedata architecture modernizationVSAvoiddata validation efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by migrating data to the modern database environment before full validation is complete. The modern database is populated with data from the legacy system in advance, allowing parallel validation operations to occur while the legacy system continues to operate. This enables modernization to proceed without waiting for complete validation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary validation system that sits between the legacy and modern database environments. This intermediary component captures data changes from the legacy system, translates them to the modern system's data model, and performs validation operations. This mediator enables validation efficiency while accommodating architectural differences between the two systems.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If parallel databases are run simultaneously for data validation, then data integrity is ensured, but system complexity increases

Engineering Contradiction:

Improvedata integrityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The validation system is segmented into distinct modular components: a data capture module that monitors the legacy database, a translation module that converts data between schemas, and a validation module that compares records. This segmentation allows each component to be independently managed and configured, reducing overall system complexity while maintaining data integrity through parallel validation.

Inventive Principle:

Principle #1Segmentation

3Stability of the object's composition

If data updates are synchronized between legacy and modern databases, then data consistency is maintained, but transition time increases

Engineering Contradiction:

Improvedata consistencyVSAvoidtransition time

Core Design Contradiction:

Stability of the object's compositionVSLoss of time

Solution Approach 1:

The system implements periodic action by synchronizing data updates at scheduled intervals rather than continuously. The validation system periodically captures data from the legacy database, compares it with the modern database state, and performs validation operations at these discrete time points. This periodic approach maintains data consistency while significantly reducing the total transition time compared to continuous synchronization.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS11803535B2Systems, methods, and apparatuses for simultaneously running parallel databases

Publication Date: 2023.10.31 CDK GLOBAL LLC

AI summary

Embodiments herein relate to replacing a legacy Pick environment with a modern microservice architecture. A legacy database and a modern database may be operated in parallel for data validation. During the validation process, the legacy database may be used as the master copy of the data. After verifying that the modern database satisfies the data needs of a system, the system can switch to using the new modern database as the master copy.