Streaming Data Pipeline Registry for Consistent Global Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Synchronizing data pipelines between computing devices, particularly when moving data from a first computing device to another due to storage constraints, is challenging as it often results in the generation of different global unique identifiers for the same event, compromising data integrity and consistency.

Innovation Solution

A system and method using a shared registry to manage global unique identifiers, ensuring that only one data pipeline successfully writes the identifier to the registry, preventing duplicate identifiers and maintaining data consistency across devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Volume of stationary object

If data is moved from a first computing device to a second computing device due to storage constraints, then data storage capacity is improved, but data consistency and integrity deteriorate due to generation of different global unique identifiers

Engineering Contradiction:
Improvedata storage capacityVSAvoiddata consistency
Core Design Contradiction:
Volume of stationary objectVSReliability

Solution Approach 1:

The patent merges the global unique identifier generation functionality across multiple computing devices by implementing a shared registry system. When data is migrated from the first computing device to the second computing device, both devices query the same registry to ensure identical global unique identifiers are generated, thereby maintaining data consistency while enabling distributed storage capacity expansion.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The registry serves as an intermediary component between the first and second computing devices during data migration. It mediates the global unique identifier generation process by providing a centralized lookup mechanism, ensuring that both devices operate from a common reference point and generate consistent identifiers without direct peer-to-peer communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If data pipelines operate in parallel across multiple computing devices, then data processing productivity is improved, but data integrity deteriorates due to potential duplicate identifier generation

Engineering Contradiction:
Improvedata processing throughputVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback mechanisms where each computing device queries the registry to check for existing global unique identifiers before generating new ones. The registry provides real-time feedback on identifier availability, allowing parallel data pipelines to coordinate their identifier generation and prevent duplicates while maintaining high processing throughput.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Before data pipelines process data in parallel, they perform preliminary actions by querying the registry to determine available global unique identifiers. This preliminary registration step ensures that subsequent parallel processing operations can proceed simultaneously without conflict, maintaining both productivity and data integrity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12547609B2Systems and methods for streaming data pipelines
Publication Date: 2026.02.10 EXPRESS SCRIPTS STRATEGIC DEVELOPMENT INC
  • US12547609B2 patent drawing
  • US12547609B2 patent drawing
  • US12547609B2 patent drawing

AI summary

A method for streaming data pipelines includes receiving, at a first update application programming interface, a global unique identifier corresponding an entity and information associated with the entity. The method also includes determining whether the global unique identifier exists in an entity database, the entity data being configured to store information associated with one or more entities and, in response to a determination that the global unique identifier does not exist in the entity database, performing a write command to write the global unique identifier to a registry. The method also includes determining whether the write command was successful, and, in response to a determination that the write command was unsuccessful: retrieving the global unique identifier written to the registry by a second update application programming interface; and updating the entity database with information associated with the global unique identifier.