Data Validation Service for Legacy Pick to Microservice Migration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The transition from a legacy database to a modern database is challenging due to incompatible data architectures, making data validation inefficient, especially when trying to compare updates between the two systems.

Innovation Solution

A data validation system that compares updates between disparate databases by using a comparison service to convert data from different formats into a common JSON format, allowing for efficient verification and synchronization of data entries between the legacy Pick database and the modern microservice system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If data validation is performed by comparing updates between legacy and modern databases with incompatible data architectures, then data accuracy is improved, but validation efficiency deteriorates due to format conversion requirements

Engineering Contradiction:

Improvedata accuracyVSAvoidvalidation efficiency

Core Design Contradiction:

Measurement precisionVSProductivity

Solution Approach 1:

The patent introduces an intermediary service layer that mediates between the legacy database and modern database. This service automatically performs data format conversion, mapping, and validation, eliminating the need for manual format alignment while ensuring data accuracy. The intermediary handles the complexity of incompatible data architectures, allowing validation to proceed efficiently without direct comparison of raw heterogeneous formats.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If direct comparison of data entries between disparate databases is performed, then validation thoroughness is improved, but system complexity increases due to handling different data structures

Engineering Contradiction:

Improvevalidation thoroughnessVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the validation process into distinct modular components: data extraction from legacy database, format conversion service, data mapping layer, validation logic, and result reporting. Each component handles a specific aspect of the validation process, making the overall system more manageable and maintainable while ensuring thorough validation through comprehensive coverage of each data transformation stage.

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

If data format conversion is performed to enable comparison between legacy and modern databases, then compatibility is improved, but processing time increases

Engineering Contradiction:

Improvedata compatibilityVSAvoidprocessing time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary data format standardization and mapping rules definition before the actual validation process begins. By pre-configuring conversion templates, mapping relationships, and validation criteria, the system eliminates the need for complex real-time conversions during validation execution. This preliminary preparation enables faster processing while maintaining full data compatibility between legacy and modern database formats.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20240354292A1Systems, methods, and apparatuses for verifying entries in disparate databases

Publication Date: 2024.10.24 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. Part of the data validation may include verifying that changes to a business object that are entered on the legacy Pick environment are similarly entered by the modern microservice architecture.