Mirage Database Instances for Abnormal Session Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database management systems face challenges in handling abnormal requests without causing adverse effects, such as process crashes, and in efficiently managing sessions between different types of database instances.
Innovation Solution
Implementing a database management system with instances of two kinds: regular and mirage instances, where request handling can be relocated between them to minimize adverse effects and optimize performance, using automated relocation based on statistical evaluation and configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all sessions are handled in regular database instances, then service quality is maintained, but adverse effects like process crashes can occur and affect availability
Solution Approach 1:
The system segments sessions into two categories: normal sessions handled by regular instances and suspicious sessions handled by mirage instances. This segmentation isolates the harmful effects of abnormal requests to specific mirage instances, preventing them from affecting the entire system or regular instances.
Solution Approach 2:
Mirage instances act as intermediary components between client applications and regular database instances. They receive and evaluate suspicious sessions, determining whether to handle them locally or forward them to regular instances, thereby protecting regular instances from adverse effects while maintaining service continuity.
2Reliability
If suspicious sessions are isolated to separate instances, then regular instances are protected, but system complexity increases with multiple instance types
Solution Approach 1:
Mirage instances are designed with multi-functionality: they can handle suspicious sessions locally, evaluate session normality, and forward normal sessions to regular instances. This universal design reduces the need for entirely separate specialized components, simplifying overall system architecture while maintaining reliability.
Solution Approach 2:
Mirage instances autonomously evaluate incoming sessions and make decisions about whether to handle them locally or forward them to regular instances. This self-service capability reduces the need for complex centralized management mechanisms, as each mirage instance independently manages its own session handling strategy.
3Productivity
If sessions are dynamically relocated between instance types, then resource utilization is optimized, but relocation overhead and decision complexity increase
Solution Approach 1:
The system performs preliminary evaluation of sessions at the mirage instance level before they reach regular instances. By pre-identifying and handling suspicious sessions at mirage instances, the system avoids the complexity of dynamic relocation decisions at regular instances, as sessions are already classified and routed appropriately.
Solution Approach 2:
The system uses feedback from session evaluation results to dynamically adjust session handling decisions. Mirage instances monitor session patterns and use this feedback to determine whether to continue handling sessions locally or forward them to regular instances, optimizing resource utilization based on real-time system state without requiring complex centralized control.
Data Source
AI summary
Instances of a database server can be of two kinds, regular or mirage that respectively handle database requests in sessions behaving normally or abnormally, and based on changes in behavior, sessions are relocated therebetween. Behavior of sessions is evaluated based on statistics generated in processing requests in individual steps within one or more stages, such as parse stage. The evaluation may be automatically tuned by changing tests that are enabled based on priorities, changing thresholds within tests, changing whether sessions are evaluated together as a group, and changing periodicity of evaluation. Evaluation may be triggered by news of normal/abnormal activity in locations of sessions' origin. Mirage instances can be of multiple classes, execute in lower/higher capacity computers. Sessions may start in either kind of instance. Sessions may be relocated for reasons unrelated to maliciousness, such as excessive utilization of resources, excessive errors, or update of software of the database server.