Service Version Cleanup via Metadata Reachability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software development platforms face challenges in managing multiple versions of services, where some versions become unreachable by service requesters, leading to unnecessary storage and resource allocation issues.
Innovation Solution
The platform employs metadata examination to identify unreachable service versions and deletes them, using XML documents with tags indicating compatibility, allowing for efficient service versioning, grouping, and cleanup.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple versions of a service are stored to maintain compatibility with different service requestors, then adaptability is improved, but storage space and resource allocation increase
Solution Approach 1:
The system automatically discards unreachable service versions by examining metadata to determine which versions are no longer compatible with any service requestors. This principle resolves the contradiction by eliminating unnecessary stored versions (reducing storage space) while preserving reachable versions that maintain compatibility (adaptability).
Solution Approach 2:
The service version management system performs self-service by automatically examining metadata, determining reachability, and deleting unreachable versions without manual intervention. This automates the balance between maintaining adaptability and reducing storage requirements.
2Adaptability or versatility
If multiple versions of a service are maintained to support different requestor versions, then versatility is improved, but device complexity increases
Solution Approach 1:
The system uses self-service by automatically examining metadata to determine service version reachability and identifying which versions should be deleted. This automated metadata-driven approach reduces version management complexity while maintaining support for multiple service requestor versions.
Solution Approach 2:
The system uses metadata as feedback information to automatically determine which service versions are reachable and which are not. This feedback mechanism enables automatic version cleanup while maintaining versatility, reducing the complexity of manual version management.
3Loss of energy
If unreachable service versions are deleted to optimize storage, then resource usage is improved, but risk of removing compatible versions increases
Solution Approach 1:
The system uses metadata examination as a feedback mechanism to determine service version reachability before deletion. By checking compatibility information in the metadata, the system ensures that only truly unreachable versions are removed, optimizing storage while maintaining reliability of compatible service versions.
Solution Approach 2:
The system performs preliminary examination of metadata to determine service version reachability before executing deletion. This preliminary action ensures that compatible versions are identified and preserved, reducing the risk of accidentally removing reachable versions while optimizing storage resources.
Data Source
AI summary
Versions of a service not reachable by a set of service requestors that use the service are removed. Multiple, different versions of a service are stored, along with metadata associated with the multiple, different versions of the service. The metadata is examined to determine one or more of the multiple, different versions of the service that are not reachable by the set of service requestors that use the service. Those versions are deleted.