Cloud On-Premises Connectivity via Virtual IP and UDP
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for establishing connectivity between cloud and on-premises systems face challenges such as unsupported connection types, unstable connections, and poor performance due to reliance on stateful TCP connections and limited underlying TCP connections.
Innovation Solution
The implementation of a system that uses virtual Internet Protocol (IP) addresses for secure, stateless connections and routing, combined with the Quick User Datagram Protocol (UDP) Internet Connection (QUIC) protocol, to provide stable, reliable, and high-performance connectivity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If reverse proxy with stateful TCP connection is used to establish cloud to on-premises connection, then secure connection is achieved, but connection stability deteriorates and connection failures occur frequently
Solution Approach 1:
The patent replaces the traditional TCP-based mechanical connection system with a UDP-based connection system. Specifically, it uses UDP sockets to establish communication channels between cloud services and on-premises data sources, eliminating the stateful TCP handshake and connection maintenance overhead. This substitution fundamentally changes the connection paradigm from reliable but complex TCP to faster and more stable UDP for this specific use case.
Solution Approach 2:
The patent introduces a gateway service as an intermediary component that sits between the cloud service and the on-premises data source. This gateway establishes and maintains the UDP connection, managing the connection state and handling reconnections automatically. By offloading connection management to this intermediary, the original cloud service and data source don't need to directly manage complex connection states, reducing their complexity while maintaining stability.
2Productivity
If reverse proxy is used for cloud to on-premises connectivity, then connection establishment is possible, but connection performance deteriorates due to limited underlying TCP connections
Solution Approach 1:
The patent replaces the TCP connection mechanism with UDP socket communication. UDP sockets don't have the same connection limits and overhead as TCP connections, allowing for higher throughput and better performance in data-intensive operations like large-scale data replication. The UDP-based approach eliminates TCP's connection state management, flow control, and retransmission overhead.
Solution Approach 2:
The patent changes the fundamental parameter of the communication protocol from TCP to UDP. This parameter change allows the system to bypass TCP's connection limits and performance constraints. By using UDP sockets with appropriate buffer sizes and non-blocking I/O, the system can handle larger volumes of data with fewer connection resources, directly improving data replication performance.
3Adaptability or versatility
If customized integration between application and reverse proxy is implemented, then unsupported connection types are supported, but implementation complexity and time increase significantly
Solution Approach 1:
The patent creates a universal gateway service that can handle multiple connection types and protocols through a single standardized interface. The gateway accepts various connection requests from different cloud services and translates them into appropriate UDP communications with on-premises data sources. This multi-functional approach eliminates the need for customized integrations for each application-gateway pair, as the gateway is designed to work with diverse connection types out of the box.
Solution Approach 2:
The gateway service acts as a universal intermediary that abstracts away the complexity of different connection types. Instead of integrating each application directly with various protocols and data sources, the application simply connects to the gateway using standard UDP sockets. The gateway then handles the complexity of supporting different connection types, protocols, and data source configurations, making the integration process simple and fast.
Data Source
AI summary
Techniques for providing connectivity between cloud and on-premises systems are disclosed. A computer system may receive, by a node of a virtual private cloud from a software application running on the virtual private cloud, a virtual host identification of a destination host running on an on-premises network, and identify, by the node, a virtual Internet Protocol (IP) address of the destination host based on the virtual host identification. Then, the computer system may send, by the node, a request comprising the virtual IP address of the destination host to a software agent running on the on-premises network, where the software agent is configured to send the request to the destination host using the virtual IP address.