Web Service Metadata Refresh Using Trigger-Based Selective Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud-based platforms, changes to a tenant's data model in a web service are not consistently reflected in the associated metadata, leading to improper invocations or data requests due to outdated metadata, and concurrent metadata refreshes can burden computer resources.
Innovation Solution
Implement a system that detects global and local trigger events to determine the extent of metadata refresh needed, using locks to manage concurrent updates and retries for unsuccessful refresh operations, thereby reducing resource usage and ensuring consistent metadata updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If metadata is refreshed frequently to ensure data consistency, then metadata reliability is improved, but computer resource consumption increases
Solution Approach 1:
The system implements periodic metadata refreshment triggered by specific events (data model changes, schema updates) rather than continuous refreshment. The metadata service monitors for trigger events and refreshes metadata only when necessary, reducing unnecessary resource consumption while maintaining consistency when changes occur.
Solution Approach 2:
The metadata refreshment system automatically detects trigger events and initiates refreshment without manual intervention. The system self-manages the refreshment process by monitoring data model changes and automatically updating metadata when required, eliminating the need for external triggering while optimizing resource usage.
2Reliability
If all metadata is refreshed completely to ensure full consistency, then metadata reliability is improved, but processing time increases
Solution Approach 1:
The metadata refreshment process is segmented into selective updates based on trigger event types. Different event types (global triggers vs. local triggers) cause different scopes of metadata to be refreshed - either all metadata or only specific portions related to the changed data model elements. This segmentation reduces the time required compared to complete refreshment while maintaining necessary consistency.
Solution Approach 2:
The system performs partial metadata refreshment based on the scope of changes detected. When only specific data model elements change, only the related metadata portions are refreshed rather than performing excessive complete refreshment. This partial action approach maintains consistency for affected metadata while significantly reducing overall processing time.
3Productivity
If concurrent metadata refresh operations are allowed to improve processing speed, then productivity is improved, but system stability deteriorates due to resource contention
Solution Approach 1:
The system acquires locks on metadata before performing refreshment operations and releases them after completion. This preliminary locking action prevents concurrent refresh operations from occurring simultaneously, eliminating resource contention and stability issues while still allowing efficient sequential processing. The lock mechanism ensures that only one refresh operation occurs at a time, maintaining system stability.
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for updating metadata associated with a data model. The data model comprises entities arranged into a plurality of entity groups. A determination is made that the data model has been changed based on either a first or second trigger event. If the determination is based on the first trigger event, the entities in the plurality of entity groups are resolved, and for the entities that resolved successfully, updated metadata is generated commensurate with the change and subsequently saved. If the determination is based on the second trigger event, a first entity group of the plurality of entity groups that is associated with the change is determined. All entities in the first entity group are resolved, and for the entities in the first entity group that resolved successfully, updated metadata commensurate with the change may be generated and subsequently saved.