Hybrid Cloud API Gateway Dynamic Data Routing

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 that includes at least one public-cloud server, one private on-premise server, and a computer system with a processor, communication interface, and memory device. This system dynamically determines the most efficient source for data access from the public-cloud server, private on-premise server, or cloud operational data store by analyzing predefined factors, and then retrieves and exposes the data for client access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is stored in a hybrid cloud environment combining public-cloud and private on-premise servers, then data management scalability is enhanced, but cloud service latency increases and data access efficiency deteriorates

Engineering Contradiction:
Improvedata management scalabilityVSAvoidcloud service latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces an API gateway as an intermediary component that sits between client devices and the hybrid cloud infrastructure. The gateway dynamically routes API calls to appropriate data sources (public-cloud servers, private on-premise servers, or cloud operational data store) based on predefined factors, thereby mediating the complex interactions and reducing access latency without sacrificing scalability

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple data sources are used in hybrid cloud infrastructure, then data availability resilience is improved, but system complexity increases making data access less user friendly

Engineering Contradiction:
Improvedata availability resilienceVSAvoiduser friendliness
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements automated self-service mechanisms where the API gateway autonomously determines the most efficient data source by analyzing predefined factors such as data location, availability status, and access patterns. This automation eliminates the need for users to manually configure or understand the complex multi-source infrastructure, maintaining user friendliness while achieving resilience through redundant data access paths

Inventive Principle:
Principle #25Self-service

3Productivity

If data access routes are dynamically determined based on predefined factors, then data access efficiency is improved, but system complexity and difficulty of detecting and measuring optimal routes increases

Engineering Contradiction:
Improvedata access efficiencyVSAvoidoptimal route determination complexity
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where the system continuously monitors data access performance, availability status, and routing outcomes. This feedback loop allows the API gateway to learn from past access patterns and dynamically adjust routing decisions, improving data access efficiency over time while the automated nature of the feedback processing keeps the system manageable despite its complexity

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250053458A1Hybrid-cloud infrastructure environment for resilient data access and processing from API call routing
Publication Date: 2025.02.13 TRUIST BANK
  • US20250053458A1 patent drawing
  • US20250053458A1 patent drawing
  • US20250053458A1 patent drawing

AI summary

Systems and methods receive, via a client device, an API call to access a portion of data and dynamically determine a most efficient source from which to source the portion of the data, where the most efficient source is selected from (i) at least one public-cloud server, (ii) at least one private on-premise server, and (iii) a cloud operational data store. This dynamic determination includes analyzing predefined factor(s). A request is transmitted to the most efficient source to access the portion of the data and the portion of the data is retrieved from the most efficient source. The portion of the data is exposed for access via the client device.