Hybrid-Cloud API Routing for Resilient Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Hybrid cloud environments face challenges with cloud service latency, user unfriendliness, and data unavailability due to service provider downtimes, necessitating improved systems and methods for resilient data access.

Innovation Solution

A hybrid-cloud infrastructure environment is implemented for API call routing, which includes public-cloud and private on-premise resources, and a computer system that transfers and loads data into a cloud operational data store, performs data enrichment, and provides data access from selected locations within the hybrid-cloud environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is stored only in on-premise private cloud resources, then data security and control are improved, but scalability and accessibility are worsened

Engineering Contradiction:
Improvedata securityVSAvoidscalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments data storage across multiple locations: on-premise private cloud resources and public cloud resources. This segmentation allows the system to maintain data security locally while enabling scalable access through multiple distributed data providers, resolving the contradiction between security and scalability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a nested architecture where on-premise private cloud resources are embedded within a broader hybrid cloud environment that includes public cloud resources. This nested structure allows local data control while providing access to external scalable resources through the hybrid cloud infrastructure.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Reliability

If data is replicated across multiple cloud providers, then data availability and resilience are improved, but system complexity is worsened

Engineering Contradiction:
Improvedata availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal hybrid cloud infrastructure that can interface with multiple different cloud providers through standardized protocols and interfaces. This multi-functional system handles data replication, routing, and access across diverse providers through a unified architecture, reducing the complexity that would otherwise arise from managing multiple separate systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces intermediary components including a data access layer and routing mechanisms that mediate between data consumers and multiple cloud providers. These intermediaries abstract the complexity of multi-provider replication, presenting a simplified interface while managing the underlying complexity of data distribution across providers.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If data access is centralized through a single cloud provider, then system simplicity is improved, but service continuity is worsened during provider downtime

Engineering Contradiction:
Improvesystem simplicityVSAvoidservice continuity
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements local quality by enabling data access from multiple geographically and organizationally distributed providers. Each provider maintains local data copies with specific characteristics, allowing the system to access data from the most appropriate local source during provider downtime while maintaining overall system simplicity through standardized access protocols.

Inventive Principle:
Principle #3Local quality

4Reliability

If data is kept in original storage locations, then data integrity is improved, but access latency is worsened

Engineering Contradiction:
Improvedata integrityVSAvoidaccess latency
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent performs preliminary actions by pre-replicating data to edge locations and distributed providers before access is needed. This advance data distribution reduces access latency when users need data, while the replication process maintains data integrity through standardized transformation and validation procedures.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250053459A1API call routing within hybrid-cloud architecture systems
Publication Date: 2025.02.13 TRUIST BANK
  • US20250053459A1 patent drawing
  • US20250053459A1 patent drawing
  • US20250053459A1 patent drawing

AI summary

Systems and methods transfer a replica of data from data provider(s), where the data provider(s) include either public-cloud resource(s) or private on-premise resource(s). The transferring includes extracting data from data provider(s) to a temporary location, transforming the extracted data into a format suitable for loading the data to a cloud operational data store, and loading the transformed data to the cloud operational data store. Further, data enrichment process(es) are performed to the replica of the data loaded to the cloud operational data store. Data access is provided, within the hybrid-cloud infrastructure environment, by routing an API call to access the data from a location selected from the group consisting of (i) the replica of the data loaded to the cloud operational data store, (ii) the on-premise resource(s), and (iii) the public-cloud resource(s).