Resource Proxy Deduplication for Kubernetes Storage Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In computer systems, especially those using orchestration systems like Kubernetes, the duplication of data object specifications leads to inefficient storage resource utilization, limiting scalability due to redundant data storage across identical or similar entities.
Innovation Solution
A resource proxy intercepts requests for data objects, performs deduplication by comparing new specifications to existing ones, and stores references instead of redundant data, reducing storage needs by reusing existing specifications and storing references, thereby improving storage efficiency and scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data object specifications are duplicated for each computing entity, then individual entity management is simplified, but storage resource utilization deteriorates due to redundant data
Solution Approach 1:
The patent merges identical specification data across multiple computing entities by storing a single copy in the database and using references/pointers to link multiple entities to that shared specification. This eliminates redundant storage while maintaining the ability to manage individual entities through their references to the shared data.
Solution Approach 2:
Instead of copying entire specification data for each entity, the system creates lightweight reference copies that point to the master specification in the database. This allows rapid entity creation and management without duplicating the actual specification content, resolving the contradiction between ease of operation and storage efficiency.
2Adaptability or versatility
If specifications are stored for each computing entity, then entity independence is improved, but scalability deteriorates due to redundant data storage
Solution Approach 1:
The system merges shared specification data across entities while maintaining entity independence through reference-based relationships. This allows the system to scale efficiently because adding new entities that share specifications does not increase storage requirements, while entities remain independently manageable through their reference links.
Solution Approach 2:
The patent implements a universal specification storage mechanism where a single specification in the database can serve multiple computing entities simultaneously. This multi-functional approach allows the same specification data to be reused across numerous entities, dramatically improving scalability while preserving entity independence through reference-based access.
3Speed
If duplicate specifications are maintained across entities, then data access speed is improved, but storage capacity deteriorates due to redundant copies
Solution Approach 1:
The system creates reference copies instead of full data copies, allowing rapid access to specification data through pointer references without duplicating the actual specification content in storage. This maintains fast data access performance while dramatically reducing the storage volume required.
Solution Approach 2:
The patent introduces a reference mechanism as an intermediary between computing entities and the master specification in the database. This reference layer enables fast access without requiring duplicate storage of the actual specification data, effectively decoupling access speed from storage capacity requirements.
Data Source
AI summary
Deduplication of specifications for data objects can be performed. For example, the resource proxy can intercept a first write request from a client device. The first write request can be for a first data object that represents a first computing entity, and can include a first status. The resource proxy can generate a specification that can be used with the first status to create the first data object. After generating the specification, the resource proxy can intercept a second write request for a second data object with a second status. The second data object can represent a second computing entity that is a same type as the first computing entity. The specification can be used with the second status to create the second data object. The resource proxy can fulfill the second write request by creating the second version of the data object using the specification and the second status.