Application Arbiter for Dynamic ISP and Data Center Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Global Server Load-Balancing (GSLB) systems fail to accommodate multipath routing effectively, leading to increased latency and inefficient resource usage when routing applications across multiple data centers and internet service providers, as they primarily focus on the application side rather than the client side, resulting in suboptimal user experiences and redundant network paths.
Innovation Solution
An application arbiter device that optimally routes application data and network traffic using a database of metrics, enabling dynamic selection of internet service providers (ISPs) and data centers, enriching DNS requests with additional metadata to consider N-path routing, and programmatically generating probes to gather crowd-sourced measurements for optimizing connection paths and reducing latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If GSLB systems use traditional DNS-based routing to select data centers, then application availability is improved, but routing latency increases and multipath routing efficiency deteriorates
Solution Approach 1:
The patent segments the routing decision process into multiple independent components: DNS-based data center selection, ISP selection, and path optimization. Each segment can be optimized independently, allowing the system to maintain reliability through DNS while reducing latency through specialized routing protocols and multiple parallel paths.
Solution Approach 2:
The patent adds a new dimension to routing by introducing ISP-level selection alongside traditional data center selection. Instead of only choosing among data centers, the system now operates in a two-dimensional space of (data center, ISP) combinations, enabling more granular control over routing paths and reducing latency through optimal path selection.
2Reliability
If GSLB systems implement failover paths with backup networking components, then application availability is improved, but resource efficiency deteriorates due to excessive redundancy
Solution Approach 1:
The patent implements self-service routing where the system automatically monitors path health, detects failures, and dynamically reroutes traffic without manual intervention. This eliminates the need for static backup components, as the system adapts in real-time to maintain availability while using resources efficiently.
Solution Approach 2:
The patent changes the parameter of redundancy from static (pre-configured backup components) to dynamic (real-time path selection based on monitored conditions). This allows the system to maintain high availability only when necessary, reducing resource waste during normal operation while quickly responding to actual failures.
3Adaptability or versatility
If routing services enable multipath routing across multiple ISPs and data centers, then routing flexibility is improved, but system complexity increases
Solution Approach 1:
The patent creates a universal routing framework that handles multiple protocols, path types, and selection criteria through a single standardized system. This multi-functional approach consolidates what would otherwise require separate specialized systems, managing complexity while maintaining high routing flexibility across diverse network conditions.
Solution Approach 2:
The patent introduces intermediary components that mediate between the complex multipath routing logic and the underlying network infrastructure. These intermediaries abstract and manage the complexity of coordinating multiple ISPs and data centers, providing a simplified interface while enabling sophisticated routing decisions.
4Productivity
If GSLB systems focus on application-side load balancing, then application performance is improved, but client-side optimization deteriorates
Solution Approach 1:
The patent performs preliminary actions on the client side by pre-selecting optimal ISPs and routing paths based on client location, network conditions, and application requirements. This upfront optimization reduces latency and improves user experience before the application even begins executing, complementing application-side performance optimization.
Data Source
AI summary
Described embodiments provide for routing remote application data. A device can receive a request to access an application. The application can be provided by data centers and accessible via service providers. The device can select a data center from the plurality of data centers and a service provider based at least on a metric indicative of a connection between the data center and the service provider. The device can query a database including one or more connection metrics using the application identified in the request and a location of a router transmitting the request. The device can determine the location of the router based on an internet protocol (IP) address of a client communicably coupled to the router. The device can transmit a response to the request identifying the selected data center and the selected service provider.