Web Service Request Routing via Performance Threshold Sandboxing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In computing systems, particularly in remote server environments, high-volume or resource-intensive web service requests can degrade the performance of other requests, leading to a progressive deterioration in service reliability and quality.
Innovation Solution
A system that routes web service requests to either a sandboxed instance or a default instance based on performance metric thresholds, isolating resource-intensive requests to prevent performance degradation, with the sandboxed instance having significantly fewer resources than the default instance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If resource-intensive web service requests are processed by the default web service instance, then the service can handle high-volume requests, but the performance of other requests deteriorates due to resource consumption
Solution Approach 1:
The patent segments web service requests into two categories: normal requests handled by the default web service instance and suspicious/resource-intensive requests handled by the sandboxed instance. This segmentation isolates problematic requests to prevent them from degrading the performance of normal requests, thus resolving the contradiction between handling high-volume requests and maintaining service performance.
Solution Approach 2:
The sandboxed web service instance acts as an intermediary for potentially harmful requests. By routing suspicious requests through this isolated sandboxed environment, the system prevents resource-intensive or malicious requests from directly impacting the default instance, thereby protecting overall service performance while still processing all requests.
2Reliability
If a sandboxed instance is created to isolate resource-intensive requests, then service reliability is maintained, but system complexity increases
Solution Approach 1:
The sandboxed web service instance serves multiple functions: it processes suspicious requests, isolates potentially harmful operations, monitors performance metrics, and prevents resource exhaustion. By consolidating these protective and monitoring functions into a single sandboxed instance, the patent reduces overall system complexity compared to creating separate isolated environments for each function.
3Reliability
If performance monitoring is continuously performed on all requests, then resource-intensive requests can be identified, but processing overhead increases
Solution Approach 1:
The patent applies partial monitoring by only performing comprehensive performance metric monitoring on requests that are routed to the sandboxed instance. Normal requests processed by the default instance do not undergo the same level of monitoring, thus reducing overall processing overhead while still maintaining the ability to identify and isolate resource-intensive requests when they occur.
Data Source
AI summary
A web service request is received, and a stored performance metric value, generated for other web service requests of the same type, is compared to a threshold value. If the stored performance metric value meets the threshold value, then the received web service request is routed to a sandboxed instance of the web service for execution. If the stored performance metric value does not meet the threshold value then the received web service request is routed to a default web service instance for execution. In either case, the performance metric is monitored during execution of the received web service request, and the stored performance metric value is updated based upon the monitored performance metric generated for the received web service request.