Cloud Storage Auxiliary Object Relational Naming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud-based storage environments lack the ability to associate objects effectively, leading to issues such as auxiliary objects not following the same lifecycle events as their related first-class objects, resulting in compliance and storage problems.
Innovation Solution
A method and system where an upload proxy and Storage Child Service (SCS) in a multi-tenant cloud-based storage environment generate identifiers for auxiliary objects by hashing the entity identifier of related first objects, allowing these objects to be stored and updated in conjunction with the first objects, ensuring synchronized lifecycle events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If auxiliary objects are uploaded as first-class user files, then they can be stored and accessed independently, but they appear in user file listings and do not follow lifecycle events of related objects
Solution Approach 1:
The patent embeds the entity identifier of the related first-class object directly within the filename of the auxiliary object. This nesting approach allows the auxiliary object to be stored independently as a first-class file while containing embedded information about its relationship to the parent object, thus resolving the contradiction between independent accessibility and association maintenance.
Solution Approach 2:
The patent introduces an upload proxy service that acts as an intermediary between the user upload process and the storage system. This proxy automatically extracts the entity identifier from uploaded files, generates appropriate filenames for auxiliary objects containing the parent object's identifier, and ensures proper association without requiring user intervention or appearing in user file listings.
2Adaptability or versatility
If no association exists on the backend, then objects can be managed independently, but auxiliary objects do not follow the same lifecycle events as related objects
Solution Approach 1:
The patent implements a feedback mechanism where the storage child service continuously monitors lifecycle events (such as deletion, move, or compliance operations) on first-class objects. When such events occur, the service automatically detects the entity identifier, locates associated auxiliary objects through filename matching, and applies the same lifecycle operations to them, ensuring compliance and consistency without breaking independent manageability.
Solution Approach 2:
The system enables auxiliary objects to self-identify their association through embedded entity identifiers in their filenames. This self-service approach allows the storage system to automatically match and manage auxiliary objects with their parent objects based on the embedded identifiers, ensuring lifecycle consistency without requiring complex external mapping tables or manual association tracking.
3Ease of manufacture
If auxiliary objects are stored separately without association, then storage operations are simple, but compliance requirements cannot be enforced across related objects
Solution Approach 1:
The upload proxy and storage child service act as intermediaries that automatically handle compliance enforcement. When compliance operations are requested on a first-class object, the intermediary service extracts the entity identifier, identifies all associated auxiliary objects through filename matching, and批量 applies the compliance operation to all related objects, maintaining simplicity while ensuring compliance.
Solution Approach 2:
The system implements feedback loops where compliance operations on first-class objects trigger automatic monitoring and identification of associated auxiliary objects through their embedded entity identifiers. The system then enforces the same compliance requirements on auxiliary objects, ensuring regulatory adherence across the entire object hierarchy without complicating storage operations.
Data Source
AI summary
Embodiments are directed to association of storage objects in a multi-tenant, cloud-based storage environment. More specifically, a first object can be made available in the file system of the environment and can be accessed, for example, by its file or object name. At some point thereafter, an auxiliary object can be provided that is related to the first object. For example, this auxiliary object can comprise metadata or other content associated with or related to the first object. According to one embodiment, this auxiliary object can be assigned an identifier that not only uniquely identifies the auxiliary object but also identifies, within the identifier itself, the relationship to the first object. This relational naming can be used to track the relationship between objects, e.g., to update the auxiliary object based on changes to the first object, but without a separate mapping of the objects.