Retention Framework for Multi-Cloud Vendor-Specific File Policies
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content management systems face challenges in providing retention operations across multiple S3 compliant cloud storage vendors due to the use of different vendor-specific protocols, necessitating separate code for each data store, which is cumbersome and inefficient.
Innovation Solution
A retention framework is introduced that couples with a content management system and multiple data stores, using a common protocol for file transfer operations while generating vendor-specific retention requests based on the identified data store's protocols, eliminating the need for individual SDKs for each vendor.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate code is provided for each S3 compliant cloud store to support retention operations, then retention functionality can be provided for each vendor, but the system becomes cumbersome and complex to maintain
Solution Approach 1:
The patent introduces a retention framework that acts as an intermediary layer between the content management system and multiple vendor-specific data stores. This framework receives retention commands in a common format and automatically translates them into vendor-specific protocols, eliminating the need for separate retention code for each vendor while maintaining full retention functionality across all S3 compliant cloud stores
Solution Approach 2:
The retention framework is designed with universal functionality to handle retention operations across multiple different vendors and protocols. By implementing a single unified framework that can adapt to various vendor-specific requirements, the system achieves multi-vendor support without requiring separate implementation for each data store, thereby reducing overall system complexity
2Reliability
If multiple vendor-specific protocols are used for retention operations, then each data store can be optimized for its vendor, but the content management system must maintain separate SDKs for each vendor
Solution Approach 1:
The retention framework serves as a mediator that handles all vendor-specific protocol interactions. It receives standardized retention commands from the content management system and automatically translates them into the appropriate vendor-specific protocols, ensuring reliable compliance with each vendor's requirements while eliminating the need for the content management system to maintain multiple vendor-specific SDKs
3Device complexity
If a common protocol is used for all data stores, then SDK dependency is reduced, but vendor-specific retention protocols cannot be properly implemented
Solution Approach 1:
The system architecture is segmented into distinct layers: a common interface layer that the content management system interacts with, and a translation layer (retention framework) that handles vendor-specific protocols. This segmentation allows the use of a common protocol at the content management level while maintaining proper vendor-specific protocol implementation at the data store level, effectively resolving the contradiction between reducing SDK dependency and ensuring protocol compatibility
Data Source
AI summary
Systems, methods and products for performing file retention operations in a system in which a content management system accesses multiple cloud-based data stores that are compliant with a common file transfer protocol, but use different vendor-specific protocols for file retention operations, where a retention framework is coupled between the content management system and the data stores. The content management system performs file access operations by accessing an SDK that generates requests for these operations which follow the common set of protocols. The content management system performs file retention operations by accessing a retention framework that uses the information received from the content management system to identify the targeted file, identify the data store in which the targeted file is stored, and generate a request for a retention operation that is configured according to the data-store-specific retention protocols which correspond to the identified data store.