Master Lock System for Enterprise Service Oriented Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The cross system lock scheme used in enterprise-level applications restricts interoperability with legacy systems and inefficiently manages resource access due to its reliance on synchronous remote function calls and tight application coupling, leading to increased network communication and resource locking, which hinders data consistency and performance.
Innovation Solution
A master lock system is introduced in an enterprise service-oriented architecture that designates a single master for each resource, granting access through a lock system and reclaiming it if not released, ensuring data coherence and improving performance by minimizing unnecessary resource locking and lock acquisition time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the cross system lock scheme is used to manage resource access, then resource locking and data consistency are maintained, but network communication overhead increases and system performance deteriorates due to synchronous remote function calls and tight coupling requirements
Solution Approach 1:
The patent introduces an intermediary locking mechanism that decouples the direct synchronous communication between systems. Instead of requiring systems to directly call each other synchronously, the lock scheme acts as an intermediary that coordinates access to shared resources, reducing network communication overhead while maintaining data consistency.
Solution Approach 2:
The patent segments the resource access control into independent lockable entities, allowing fine-grained control over specific resources rather than requiring broad synchronous coordination across entire systems. This segmentation enables parallel access to different resources, improving overall system performance while maintaining consistency for each segmented resource.
2Reliability
If the cross system lock scheme requires synchronous remote function calls and tight application coupling, then resource access control is enforced, but interoperability with legacy systems is restricted
Solution Approach 1:
The patent creates a universal locking interface that can work with different system architectures and communication protocols. The lock scheme is designed to be protocol-agnostic, allowing it to interface with both modern service-oriented architectures and legacy systems through adaptable communication mechanisms, thereby achieving broad interoperability while maintaining resource access control.
Solution Approach 2:
The patent employs configurable parameters and adaptable communication modes that can be adjusted to match the capabilities of different systems. By changing communication parameters (synchronous/asynchronous modes, protocol types), the locking mechanism can accommodate legacy systems with varying technical requirements without sacrificing resource access control reliability.
3Reliability
If a single document level locking is implemented at the header level, then data consistency across the entire document is ensured, but resource availability and access efficiency are reduced due to unnecessary locking of the entire document
Solution Approach 1:
The patent segments the document-level resource into finer-grained lockable units, allowing systems to acquire locks only on the specific portions of the document they need to access or modify. This segmentation enables parallel access to different document sections, reducing lock acquisition time and improving resource availability while maintaining data consistency within each locked segment.
4Reliability
If the token holder continues to use the resource through normal operation or error, then resource access is maintained for the current system, but other systems are unable to gain access to the resource
Solution Approach 1:
The patent implements periodic lock validation and timeout mechanisms that automatically release locks if the resource holder fails to renew them within specified time intervals. This periodic action ensures that resources are not permanently held by systems experiencing errors or normal operation delays, maintaining resource availability for other systems while ensuring stable access for legitimate users within the timeout period.
Data Source
AI summary
A system and process that manages access to a resource in an enterprise service-oriented architecture environment. The system recognizes a master for each resource that has ultimate control over the respective resource. The master grants access to the resource though a lock system. If a system does not relinquish access to the resource, then the master is able to reclaim the lock to ensure the continued availability of the resource to all systems. This system ensures data coherency, while also improving performance by diminishing the amount of time a resource is unnecessarily locked and the time to obtain a lock.