Scanner Service for Legacy Database Data Validation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The transition from a legacy database to a modern database is inefficient due to incompatible data architectures, making it difficult to validate updates across both systems, especially when handling a large number of updates in legacy databases like the Pick environment.

Innovation Solution

A scanner service is implemented to scan records in the legacy database, filter and combine updates based on business objects, and convert them into efficient update messages for the modern database, allowing for parallel operation and data validation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a legacy database and a modern database are run in parallel for data validation, then data validation capability is improved, but system complexity increases due to incompatible data architectures

Engineering Contradiction:

Improvedata validation capabilityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a translation layer that acts as an intermediary between the legacy database and the modern database. This translation layer converts legacy database schemas and data formats into modern database equivalents, enabling the two incompatible systems to communicate and validate data against each other without direct integration complexity

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into distinct components: the legacy database system, the translation layer, and the modern database system. Each component operates independently with well-defined interfaces, allowing parallel operation for validation while managing complexity through modular architecture

Inventive Principle:

Principle #1Segmentation

2Reliability

If all updates in the legacy database are tracked and validated, then data validation completeness is improved, but processing time increases due to the large number of updates

Engineering Contradiction:

Improvevalidation completenessVSAvoidprocessing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system implements selective validation by identifying and validating only the critical subset of updates that impact data integrity, rather than processing every single update. This partial action approach maintains validation completeness for essential data while reducing overall processing time

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The translation layer pre-processed legacy database schemas and established mapping relationships before validation begins. This preliminary action enables efficient real-time validation by having translation rules ready, rather than translating on-the-fly during validation processing

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11514021B2Systems, methods, and apparatuses for scanning a legacy database

Publication Date: 2022.11.29 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 scanning the legacy database for updates to items stored thereon. Embodiments herein may generate an update message by combining item keys from across the multiple files that correspond with a same business object.