Context-Based Lock Mode Selection for Shared Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies struggle to dynamically manage lock modes in data-sharing environments, which can vary by client, location, and time, leading to inefficiencies and inconsistencies in data access.
Innovation Solution
A lock mode determination service that dynamically determines lock modes based on criteria such as device type, location, and time of day, using a sorted checklist of evaluation criteria to ensure consistent and efficient data access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a single lock mode is used for all data access requests, then system simplicity is maintained, but data access efficiency and consistency cannot be optimized for different contexts
Solution Approach 1:
The system dynamically determines lock modes based on contextual factors such as device type, location, and time of day. The lock mode determination service evaluates multiple criteria and selects appropriate lock modes (pessimistic or optimistic) in real-time, allowing the system to adapt to different data-sharing environments and client characteristics rather than using a static lock mode configuration
Solution Approach 2:
Different lock modes are assigned to different data access requests based on specific contextual conditions. Mobile devices in motion receive optimistic locking, while stationary devices receive pessimistic locking. This allows each data access operation to have a lock mode tailored to its specific context, optimizing performance for each case without imposing complexity on the entire system
2Productivity
If optimistic locking is used to increase data availability, then data access efficiency improves, but data consistency may be compromised
Solution Approach 1:
The system changes the lock mode parameter dynamically based on contextual evaluation. When a mobile device is determined to be in motion (based on location changes over time), optimistic locking is applied to maximize availability. When the device is stationary or in locations where consistency is critical, pessimistic locking is applied to ensure data consistency. This parameter change resolves the contradiction by adapting the locking strategy to the specific situation
3Productivity
If context-based lock mode determination is implemented, then data access optimization improves, but system complexity and processing overhead increase
Solution Approach 1:
The lock mode determination process is segmented into distinct evaluation stages. The system first determines device type (mobile vs. stationary), then evaluates location context, and finally assesses motion status. Each segmentation step builds on the previous one, allowing the system to efficiently narrow down the appropriate lock mode without evaluating all possible criteria simultaneously, thus managing complexity through structured decomposition
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and systems are disclosed for flexibly managing lock modes in a data-sharing environment, including optimistic and pessimistic lock modes. A lock mode determination service receives a request from an application instance for a lock mode with which to access specified data objects. The service can determine and provide a suitable lock mode based on a context of the application, and optionally other parameters, by evaluating a checklist of criteria sorted in precedential order. Criteria can include geo-boundaries, platform, role, and others. The requesting application instance uses the determined lock mode to access the data, with optional assistance of a lock service. The lock mode determination service can support one or more applications having one or more instances each, and can also support multiple disjoint data-sharing environments. Suitable environments include cloud, datacenter, mobile, client-server, and SAAS.