ReST Framework for Heterogeneous Cloud Storage Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating cloud storage with content management systems is complex due to the need for multiple plug-ins for different cloud storage providers, leading to tightly coupled systems, increased development time, and potential downtime for updates, as well as larger binary sizes and memory footprints.
Innovation Solution
A Representational State Transfer (ReST) framework that allows dynamic consumption of ReST-based stores using configurable files, enabling support for heterogeneous ReST APIs without requiring server restarts or redeployment, and eliminating the need for dependency libraries, thus allowing seamless integration and updates of new ReST-based stores.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple plug-ins are used to support different cloud storage providers, then compatibility with various cloud stores is improved, but device complexity and binary size increase significantly
Solution Approach 1:
The patent implements a universal plug-in architecture where a single content server plug-in can communicate with multiple different cloud storage providers through standardized interfaces. The plug-in uses configuration files to adapt to different cloud stores without requiring separate plug-in code for each provider, thus achieving multi-functionality while maintaining low system complexity
Solution Approach 2:
The patent introduces configuration files as intermediaries between the plug-in and cloud storage APIs. These configuration files contain provider-specific connection details and API mappings, allowing the plug-in to adapt to different cloud stores without hardcoding provider-specific logic, thereby reducing binary size while maintaining versatility
2Adaptability or versatility
If separate plug-ins are developed for each cloud storage provider, then specific store integration is improved, but ease of manufacture and development time worsen
Solution Approach 1:
The patent creates a universal plug-in that can integrate with multiple cloud storage providers through a standardized interface. The plug-in uses configuration files to adapt to different providers, eliminating the need to develop separate plug-ins for each cloud store and significantly reducing development time
Solution Approach 2:
The patent uses configuration files that contain adjustable parameters for different cloud storage providers. By changing configuration file parameters rather than code, the plug-in can adapt to new providers quickly, making the integration process much easier and faster
3Reliability
If cloud storage APIs are tightly coupled with the content management system, then integration stability is improved, but adaptability to new stores and API changes worsens
Solution Approach 1:
The patent introduces configuration files as intermediaries that decouple the plug-in from cloud storage APIs. The plug-in communicates with cloud stores through standardized interfaces defined in configuration files, allowing stable integration while maintaining flexibility to adapt to new stores and API changes without modifying core system code
Solution Approach 2:
The patent makes the system dynamic by allowing configuration files to be updated at runtime without requiring server restarts. This enables the system to adapt to new cloud storage providers and API changes while maintaining stable operations, as the plug-in can load new configurations dynamically
4Adaptability or versatility
If the system supports multiple cloud storage providers with separate plug-ins, then store compatibility is improved, but memory usage and binary size increase
Solution Approach 1:
The patent extracts provider-specific configuration details into separate configuration files, removing the need to embed multiple sets of provider-specific code in the binary. This reduces binary size while maintaining multi-provider support through a single plug-in that reads configurations at runtime
Solution Approach 2:
The patent uses configuration files as lightweight copies of provider-specific settings and API mappings. Instead of duplicating full plug-in code for each provider, the system uses small configuration files that define provider behavior, significantly reducing the quantity of data stored while maintaining full multi-provider functionality
Data Source
AI summary
Embodiments provide systems and methods for a generic representational state transfer (ReST) framework that can be used to communicate with heterogeneous ReST interfaces. On embodiment of a method comprises storing endpoint configurations for heterogeneous ReST interfaces as configurable files consumable by a ReST framework; receiving, by the ReST framework, a request to perform an operation and ReST resource details associated with the request to perform the operation; generating a ReST request, the ReST request including an endpoint URL for a target resource, a Hypertext Transfer Protocol (HTTP) method, and a header; and sending the ReST request to a ReST server. Generating the ReST request can comprise accessing the first endpoint configuration and extract first endpoint configuration data that is applicable to servicing the request to perform the operation, the first endpoint configuration data specifying the header; and mapping the operation to the HTTP method.