Hybrid Cloud Resource Routing With Webhook-Based Low-Latency DNS

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing cloud computing environments face challenges in seamlessly integrating client computing systems with hybrid clouds, particularly in orchestrating container deployment and resource sharing across clients with varying capabilities, leading to suboptimal performance and latency issues.

Innovation Solution

A low latency mechanism using webhooks to synchronize and redirect service requests to available resources within a hybrid cloud, leveraging a webhook mechanism to update local resource pools and intercept DNS requests for efficient resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service requests are routed through remote cloud services in hybrid cloud environments, then resource sharing and scalability are improved, but latency and data transition overhead increase

Engineering Contradiction:

Improveresource sharing capabilityVSAvoidservice request latency

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-synchronizes resource pool information from remote cloud to local edge devices using webhooks before service requests are made. This preliminary action ensures that local devices have up-to-date information about available resources, enabling immediate local routing decisions without requiring real-time communication with remote cloud, thus reducing latency while maintaining resource sharing capability

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces a local resource pool and webhook mechanism as an intermediary between client computing systems and remote cloud services. This intermediary enables local devices to autonomously manage and route service requests to appropriate resources within the local hybrid cloud environment, eliminating the need for direct remote cloud communication for routine service requests and thereby reducing data transition overhead

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If local resource pools are continuously synchronized with remote cloud, then resource availability information is up-to-date, but network traffic and synchronization overhead increase

Engineering Contradiction:

Improveresource pool accuracyVSAvoidsynchronization overhead

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system implements event-driven periodic synchronization using webhooks, where the local resource pool is updated only when specific events occur (such as resource availability changes). This approach maintains resource pool accuracy by synchronizing information at appropriate intervals based on actual changes rather than continuous polling, thereby reducing network traffic and synchronization overhead while ensuring reliability

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS20250350658A1Low latency mechanism for cloud to computing system hybrid cloud

Publication Date: 2025.11.13 INTEL CORP

AI summary

The disclosure includes receiving one or more updates to a global resource pool of a hybrid cloud and updating a local resource pool with the one or more updates to the global resource pool; intercepting a service request from an application; redirecting deployment of the service request to a resource provider of the hybrid cloud with available computing resources to fulfill the service request based at least in part on the local resource pool and by using a webhook; receiving an Internet Protocol (IP) address of the resource provider; redirecting a domain name service (DNS) of the application to the IP address of the resource provider; and sending the service request to the resource provider.