Cloud Connection Parking via Server Portion Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud applications face scalability issues due to the resource-intensive nature of maintaining persistent connections between client devices and cloud servers, where connections are often idle, leading to resource wastage and decreased server performance.
Innovation Solution
A connection parking scheme is implemented, where the server portion of idle connections is partially closed using a connection interrupter and maintainer module, releasing resources while maintaining the client portion through keepalive responses, allowing for efficient reconnection upon service requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If persistent connections are maintained between client devices and cloud servers, then connection reliability and service delivery are improved, but server resource consumption increases
Solution Approach 1:
The connection is segmented into two independent parts: client portion and server portion. The connection interrupter closes only the server portion of idle connections while keeping the client portion open, allowing selective resource management without sacrificing connection reliability.
Solution Approach 2:
A connection interrupter module is introduced as an intermediary between the cloud server and client devices. This mediator selectively closes server portions of connections based on idle detection, managing resources without directly terminating client connections.
2Productivity
If all connections are fully closed to release resources, then server scalability is improved, but connection integrity and service delivery are compromised
Solution Approach 1:
By segmenting the connection into client and server portions, the system can close only the server portion for scalability while maintaining the client portion for connection integrity, avoiding the need to close entire connections.
Solution Approach 2:
Different portions of the connection have different states: the client portion remains open to maintain connection integrity, while the server portion is closed to release resources and improve scalability.
3Quantity of substance
If connection parking is implemented to close server portions, then resource conservation is improved, but connection management complexity increases
Solution Approach 1:
The connection interrupter module serves as a dedicated intermediary that handles the complexity of selectively closing server portions and managing keepalive responses, shielding the rest of the system from connection management complexity.
Solution Approach 2:
The connection maintainer automatically sends keepalive responses to maintain client portions of connections without requiring manual intervention, allowing the system to self-manage connection states.
Data Source
AI summary
Examples relate to scaling persistent connections for cloud computing. In some examples, a data packet is used to determine connection information of the first connection. At this stage, server portion of the first connection is closed by using the connection information to send a close command to the cloud server. In response to a keepalive signal from the client computing device, the connection information is used to send a keepalive response to the client computing device to maintain a client portion of the first connection. In response to a service request from the client computing device, a service notification including the service request is sent to the client computing device, where the client computing device initiates a second connection with the cloud server to process the service request.