SOA Layer File Transfer Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise service-oriented architectures for large file handling, a bottleneck occurs when users access and manage files through a Service-Oriented Architecture (SOA) layer, as large files must be routed through intermediaries, leading to inefficiencies, especially in multi-user environments.
Innovation Solution
Implementing a process where user-generated interfaces communicate directly with the enterprise-level software system to obtain a uniform resource locator (URL) for file locations on content servers, allowing direct HTTP communication with these servers for file creation, access, and storage, thereby reducing the data transferred through the SOA layer to only metadata and identifying information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all file transfers are routed through the SOA layer and KPRO intermediary, then centralized control and metadata management are maintained, but system performance deteriorates due to bottlenecks when large files are transferred
Solution Approach 1:
The patent segments the file transfer process into two distinct paths: metadata and control information continue to flow through the SOA layer and KPRO for centralized management, while large file data is transferred directly between the client and content server. This segmentation allows the system to maintain centralized control for small data packets while enabling high-speed direct transfer for large files, resolving the bottleneck issue.
2Speed
If direct HTTP communication with content servers is implemented, then file transfer speed improves, but system complexity increases due to additional communication channels
Solution Approach 1:
The patent introduces a file transfer service as an intermediary component that mediates between the client and content server. This service receives file transfer requests from the client, establishes direct HTTP connections to the content server, and coordinates the transfer process. The intermediary approach simplifies client complexity while enabling direct high-speed communication, as the client only needs to interact with the file transfer service rather than directly managing complex server communications.
3Loss of information
If large files are transferred through the SOA layer, then centralized metadata management is maintained, but network bandwidth is wasted as the same file data traverses multiple channels
Solution Approach 1:
The patent segments data transmission into metadata (which requires centralized management) and file content (which can be transferred directly). Metadata about the files is transmitted through the SOA layer to maintain centralized control and tracking, while the actual large file data is transferred directly between client and content server. This eliminates redundant transmission of file data through multiple channels while preserving metadata management capabilities.
Data Source
AI summary
A computer-implemented method of storing an object received from a client device on one or more content servers remote from the client device includes receiving, through a service oriented (SOA) layer, object metadata about the object from a non-proprietary interface running on the client device and generating a uniform resource locator (URL) with which to retrieve the object. The URL and metadata for locating and retrieving the object from a web application server are transmitted to the client device through the non-proprietary interface, and the metadata for locating and retrieving the object is transmitted through the service oriented architecture (SOA) layer to the client device. The object is received from the client device, and the object is not transmitted through the SOA layer. Finally, the object is stored on at least one of the remote content servers.