Communication Graph Tracking for Heterogeneous Database Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-system operations involving heterogeneous databases, it is challenging to track and consolidate database changes across multiple systems, leading to inconsistent states and performance issues due to the complexity of managing transactions across diverse database systems, particularly when two-phase commit protocols are not feasible or efficient.

Innovation Solution

A system that uses a streaming module to extract correlation identifiers from database commit logs, creating event streams that are stored and reconciled to generate communication graphs, allowing for the tracking and display of multi-system operations without requiring operational constraint conditions or synchronization delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If two-phase commit protocol is used to ensure atomicity across multiple database systems, then reliability is improved, but productivity deteriorates due to synchronization delays

Engineering Contradiction:
Improveatomicity guaranteeVSAvoidtransaction throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the atomicity guarantee mechanism into individual database systems, allowing each system to independently manage its own transactions without requiring synchronization with other systems. This is achieved by tracking database changes through event streams and correlation identifiers rather than through centralized two-phase commit coordination, thereby eliminating synchronization delays while maintaining reliability through alternative tracking mechanisms.

Inventive Principle:
Principle #1Segmentation

2Reliability

If operational constraint conditions are formulated to prevent inconsistent states, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improveconsistency maintenanceVSAvoidconstraint formulation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent enables database systems to self-track their own changes through event streams and correlation identifiers embedded in commit logs. Each database system automatically generates and propagates its own change events without requiring external constraint formulation or validation, thereby maintaining consistency through self-service mechanisms rather than complex inter-system constraint coordination.

Inventive Principle:
Principle #25Self-service

3Productivity

If event streams are propagated asynchronously between database systems, then productivity is improved, but reliability deteriorates due to potential inconsistent states

Engineering Contradiction:
Improvetransaction processing speedVSAvoidstate consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where database systems continuously propagate change events through event streams and allow receiving systems to track and reconcile changes using correlation identifiers. This feedback loop enables asynchronous operation while maintaining consistency through continuous monitoring and reconciliation, rather than requiring synchronous coordination that would reduce productivity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10733180B2Communication graph tracking of multi-system operations in heterogeneous database systems
Publication Date: 2020.08.04 LENDINGCLUB BANK NAT ASSOC
  • US10733180B2 patent drawing
  • US10733180B2 patent drawing
  • US10733180B2 patent drawing

AI summary

Techniques a provided for communication graph tracking in multi system operation in heterogeneous database systems, including retrieving two or more database commit logs from two or more corresponding heterogeneous databases. For each of the commit logs, a subset of information is extracted, including a correlation identifier, and event stream entries are produced based on that information and are stored. The event stream entries are then retrieved and event database entries are created based on the event stream entries. A request for a communication graph related to a particular correlation identifier is received and the event database is searched for matching entries. Those entries are used to generate a displayable communication graph for the particular correlation identifier, which is then provided in response to the request.