Soft Exit State for Secondary Business Object Locks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in efficiently managing locks on business objects, leading to performance degradation due to over-locking or under-locking, and require substantial processing time to track lock/unlock status, especially when dealing with hundreds of secondary business objects.
Innovation Solution
Implementing a 'soft exit' state for secondary business object locks, where locked objects wait for a database commit to automatically remove their own locks, reducing the processing burden on primary business objects and preventing unnecessary locking.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If locks are placed on secondary business objects to prevent simultaneous access, then data consistency is maintained, but system performance degrades due to over-locking and extended processing time
Solution Approach 1:
The secondary business object automatically manages its own lock state by detecting database commit events and self-unlocking, eliminating the need for primary business objects to manually manage locks on numerous secondary objects. This self-service mechanism reduces processing overhead while maintaining data consistency.
Solution Approach 2:
The locking mechanism is segmented into automatic self-management at the secondary object level rather than centralized management at the primary object level. Each secondary business object independently tracks its lock status and performs self-unlocking, distributing the management burden and reducing overall system complexity.
2Reliability
If locks are placed on hundreds of secondary business objects, then data consistency is maintained, but processing time and complexity increase substantially
Solution Approach 1:
Secondary business objects autonomously manage their own lock states by detecting database commit events and performing self-unlocking operations. This eliminates the complex tracking and management burden that would otherwise fall on primary business objects when dealing with hundreds of secondary objects.
Solution Approach 2:
Instead of primary business objects managing locks on secondary objects, the approach is inverted so that secondary business objects manage their own locks automatically through database commit event detection and self-unlocking mechanisms.
3Reliability
If locks are held for extended periods to ensure transaction completion, then data consistency is maintained, but system throughput decreases due to unnecessary locking
Solution Approach 1:
The system uses database commit events as feedback signals to trigger automatic unlock operations. When a database commit occurs, secondary business objects detect this event and automatically remove their locks, ensuring locks are held only for the necessary duration while maintaining data consistency.
Solution Approach 2:
Secondary business objects are pre-configured with automatic unlock logic that triggers upon detecting a database commit event. This preliminary setup ensures that locks are automatically released at the appropriate moment without requiring extended holding periods or manual intervention.
Data Source
AI summary
According to some embodiments, a primary business object BOA is established along with a plurality of secondary business objects that depend from the primary business object BOA in a hierarchy. The primary business object BOA may place a lock on a secondary business object BOB and facilitate an update of data associated with the secondary business object BOB. The secondary business object BOB may then detect when a database commit has been executed, responsive to that detection, the secondary business object BOB may remove the lock associated with the secondary business object BOB.