Unblocking Computer Resource Usage Count via Hybrid Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud computing systems face processing delays and quota violations due to frequent requests to add or remove user accounts, leading to serialized processing and potential violations of user account limits, which can result in inefficient resource management and increased latency.
Innovation Solution
Implementing a hybrid approach using eventually consistent and strongly consistent counts to manage user account quotas, allowing for parallel processing of requests and reducing the need for frequent updates, thereby minimizing latency and improving resource management efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If frequent updates to user account counts are implemented to maintain accurate quota tracking, then measurement precision is improved, but processing speed deteriorates due to serialized processing requirements
Solution Approach 1:
The system pre-calculates and caches user account counts before quota evaluation is needed. When a user requests to attach or detach a role, the system has already prepared the count information, eliminating the need for real-time calculation and enabling faster processing while maintaining accuracy.
Solution Approach 2:
The system implements background processes that continuously update and maintain user account counts in real-time as users attach or detach roles. This continuous maintenance ensures that when quota evaluation is needed, the count information is already current and accurate, eliminating the need for serialized processing to ensure data consistency.
2Reliability
If serialized processing is used to ensure accurate quota evaluation, then reliability is improved, but productivity deteriorates due to processing delays
Solution Approach 1:
The system pre-evaluates quota availability by calculating user account counts before multiple users attempt to attach roles. This preliminary evaluation ensures that quota constraints are accurately enforced while allowing users to submit requests in parallel, improving throughput without sacrificing reliability.
Solution Approach 2:
The system introduces a background evaluation process that acts as an intermediary between role attachment requests and quota enforcement. This background process continuously monitors and evaluates quota conditions, allowing the main request processing to proceed in parallel while maintaining accurate quota control through the intermediary evaluation layer.
3Measurement precision
If real-time count updates are performed for each user action, then measurement precision is improved, but loss of time increases due to frequent processing interruptions
Solution Approach 1:
The system pre-calculates user account counts and caches them before they are needed for quota evaluation. This preliminary calculation eliminates the need for real-time updates during request processing, reducing wait time while maintaining count accuracy through the pre-computed values.
Solution Approach 2:
The system implements periodic background processes that update user account counts at regular intervals or in response to specific events (such as role attachment or detachment). This periodic update approach ensures counts remain accurate without requiring continuous real-time updates, reducing processing interruptions and wait time.
Data Source
AI summary
Systems, devices, and methods are provided for unblocking a computer resource usage count. A system may receive a request for a user account and a user account policy, and may obtain a count of a first number of user accounts, wherein the count is based on an aggregation of two or more actions associated with the user account policy. The system may determine, based on the count, that the first number of user accounts is less than a threshold number of accounts. The system may obtain based on the determination that the first number of user accounts is less than the threshold number of accounts, an event history. The system may determine, based on the event history, a second number of user accounts. The system may determine that the second number of user accounts is less than the threshold number of accounts, and may update the user account policy.