Persistent Request Property Storage for Cloud Server Malfunction Blocking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud computing server malfunctions can disrupt service availability due to various errors, leading to increased response times and decreased reliability for end-users, as malfunctions can be caused by software bugs, hardware failures, or other issues, affecting multiple users sharing the same resource.
Innovation Solution
Storing properties of requests in persistent storage that retains data during malfunctions and restarts allows for blocking of similar requests in the future, reducing the frequency of server computer malfunctions by identifying and isolating problematic requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If server computers process requests in a multi-tenant cloud environment, then service availability and user access are improved, but server malfunctions increase due to software bugs, hardware failures, or other issues
Solution Approach 1:
The system stores properties of requests being processed in persistent storage before malfunctions can occur. This preliminary action ensures that when a malfunction happens, the system already has the information needed to identify and block problematic requests, preventing future occurrences without requiring complex real-time analysis during malfunction events
Solution Approach 2:
The system implements a feedback mechanism where properties of requests are stored in persistent storage, retrieved after malfunctions, and used to block similar future requests. This closed-loop feedback allows the system to learn from past malfunctions and automatically prevent their recurrence, improving reliability over time while maintaining high service availability
2Loss of time
If server computers process multiple user requests concurrently, then response time for individual users decreases, but the frequency of server malfunctions increases
Solution Approach 1:
The system extracts and stores the properties of requests that cause malfunctions in persistent storage. By separating the identification of problematic request properties from the main request processing flow, the system can quickly block malicious requests without impacting the response time for legitimate concurrent user requests
Solution Approach 2:
The persistent storage acts as an intermediary between request processing and malfunction analysis. It stores request properties during normal high-speed processing and provides them for analysis after malfunctions, enabling the system to maintain fast concurrent processing while still being able to identify and block problematic requests
3Reliability
If the system blocks requests to prevent future malfunctions, then service reliability improves, but the complexity of request processing increases
Solution Approach 1:
The system applies blocking only to requests with specific properties that were identified as causing malfunctions, rather than implementing complex global analysis of all requests. This localized approach focuses computational resources only on identifying and blocking problematic request patterns, maintaining simplicity for the majority of normal requests
Data Source
AI summary
The following description is directed to storing properties of requests to potentially block future requests having similar properties. In one example, a request can be received. A property of the request can be stored so that the property persists across an initialization sequence of a computer system. At least the property can be used to determine whether to block any future requests having similar properties.