Mixed Cache Retrieval for Low-Latency Local Authorization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud service authorization processes face inefficiencies due to unsatisfactory customer experiences resulting from different authorization processes and permissions, particularly in object storage services, leading to increased traffic and latency in identity data planes.
Innovation Solution
Implementing a local authorization client with a cache system that evaluates authorization requests using cached metadata, checks data freshness, and asynchronously or synchronously updates cache data to maintain low latency and improve user experience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If authorization requests are evaluated centrally through identity data planes, then authorization control is centralized and secure, but latency increases and system efficiency decreases
Solution Approach 1:
The patent implements local authorization clients at edge locations that evaluate authorization requests using cached metadata locally, rather than requiring all requests to traverse the central identity data plane. This local evaluation capability reduces latency while maintaining authorization control through periodic cache updates and validity checks.
Solution Approach 2:
The system pre-loads authorization metadata into local caches before it is needed for request evaluation. By maintaining pre-cached authorization data with validity timestamps, the system prepares authorization information in advance, allowing rapid local evaluation without real-time central queries, thus reducing latency while preserving security.
2Measurement precision
If cache data is frequently updated to maintain freshness, then authorization accuracy improves, but traffic to identity data planes increases
Solution Approach 1:
The system implements periodic cache updates based on validity timestamps rather than continuous synchronization. Local authorization clients evaluate whether cached metadata is still valid by checking timestamps, and only request updates when necessary. This periodic update mechanism maintains authorization accuracy while significantly reducing unnecessary traffic to identity data planes.
Solution Approach 2:
The system updates only the specific cache entries that have expired or are approaching expiration, rather than performing full cache synchronization. By selectively updating individual metadata entries based on their validity timestamps, the system maintains authorization accuracy for active entries while minimizing unnecessary data transmission.
3Productivity
If multiple authorization requests are processed simultaneously, then system throughput increases, but cache consistency problems arise
Solution Approach 1:
The system introduces validity timestamps as an intermediary mechanism to manage cache consistency during parallel operations. Each cache entry carries a timestamp indicating its validity period, allowing multiple authorization requests to be processed simultaneously using cached data while ensuring that stale data is not used. The timestamp acts as a mediator that coordinates cache usage without requiring centralized locking.
Solution Approach 2:
Local authorization clients autonomously determine whether their cached metadata is still valid by checking timestamps against current time, without requiring centralized coordination for each access decision. This self-service validity check enables parallel request processing while maintaining cache consistency, as each client independently validates its own cache state.
Data Source
AI summary
Techniques are described for evaluating an authorization request on a local computer system. An example technique can include a system, receiving an authorization request from a user device. The system can determine that authorization data, stored in a cache, does not comply with a timing threshold. In accordance with the determination that they authorization data stored in the cache does not comply with the timing threshold, the system can request updated authorization data corresponding to the authorization data that does not comply with the timing threshold. The system can determine a timing for the request. The system can implement a lock configured to block subsequent requests for the updated data. The system can execute the request for the updated authorization data according to the timing. The system can store the updated authorization data in the cache.