Retention Framework for Multi-Cloud File Retention Operations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content management systems face challenges in providing retention operations across multiple S3 compatible cloud storage vendors due to the use of different vendor-specific protocols, necessitating separate SDKs 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 access 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
1Reliability
If separate SDKs are provided for each S3 compliant data store vendor, then retention operations can be performed on each vendor's data store, but the system complexity increases and ease of operation deteriorates
Solution Approach 1:
The patent creates a universal retention framework that can perform retention operations across multiple S3 compliant data store vendors through a single unified interface. The framework translates vendor-specific retention protocols into a common retention command format, allowing one SDK to interact with multiple different vendors' data stores without requiring separate SDKs for each vendor.
Solution Approach 2:
The retention framework acts as an intermediary layer between the content management system and the various vendor-specific data stores. It receives retention commands in a common format from the content management system, translates them into vendor-specific protocols, and communicates with the appropriate data store, thereby eliminating the need for direct vendor-specific SDK integration.
2Adaptability or versatility
If separate SDKs are provided for each S3 compliant data store vendor, then vendor-specific retention protocols can be supported, but ease of operation deteriorates due to cumbersome SDK management
Solution Approach 1:
The framework provides a universal interface that supports multiple vendor protocols through a single SDK. The content management system interacts with the framework using a common retention command format, and the framework handles the complexity of translating these commands into vendor-specific protocols, making the system both adaptable to multiple vendors and easy to operate.
Solution Approach 2:
The patent segments the retention operation complexity into two distinct layers: a simple common interface layer for the content management system and a complex vendor-specific protocol layer for the data stores. The retention framework sits between these layers, handling all vendor-specific protocol complexities, while the content management system only needs to understand the simple common format.
3Ease of operation
If a common retention protocol is used across all data stores, then ease of operation improves, but adaptability to vendor-specific protocols deteriorates
Solution Approach 1:
The retention framework serves as an intermediary that receives simple common-format retention commands from the content management system and translates them into vendor-specific protocols for execution. This allows the content management system to use a simple common interface while the framework ensures compatibility with various vendor-specific protocols through automatic translation.
Solution Approach 2:
The framework changes the format parameters of retention commands based on the target vendor. It accepts retention commands in a standard common format and dynamically transforms them into the appropriate vendor-specific protocol format, thereby maintaining both ease of operation with a common interface and adaptability to different vendors through parameter transformation.
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.