Shared Storage for SOA Security and Bandwidth
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Service-oriented Architecture (SOA) and Enterprise Service Bus (ESB) systems face challenges with security, bandwidth, latency, and data persistence, particularly in large-scale distributed computing environments with heterogeneous hardware and software components, leading to limitations in scalability and reliability.
Innovation Solution
Implementing a system that utilizes shared storage to host services and infrastructure functions, enabling a robust, high-performance ESB and SOA by separating data and file system metadata, providing secure, scalable, and persistent data management through a federated metadata database, and allowing asynchronous communication and access control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a data guard performs deep packet inspection to secure SOA communications, then security is improved, but bandwidth is limited and latency increases
Solution Approach 1:
The patent extracts security inspection functionality from the data guard and relocates it to the shared storage system. The shared storage performs security inspection locally on data packets before they are written to or read from storage, eliminating the need for continuous network-based deep packet inspection. This extraction resolves the bandwidth-latency tradeoff by performing security functions at the storage layer rather than the network layer.
Solution Approach 2:
The shared storage acts as an intermediary between network communications and data persistence. It receives data packets from the network, performs security inspection, and only writes authorized data to storage. This intermediary role allows the system to maintain security while enabling higher bandwidth by filtering out unauthorized data before it consumes storage resources.
2Reliability
If a data guard inspects and processes data packets at high speed, then security coverage is improved, but latency increases
Solution Approach 1:
The shared storage performs security inspection in advance before data is written to storage and before reading from storage. By performing this preliminary action at the point of data access rather than during network transmission, the system reduces latency while maintaining comprehensive security coverage.
3Adaptability or versatility
If SOA sessions transmit all user messages across networks, then communication flexibility is improved, but data persistence and retrieval are lost
Solution Approach 1:
The patent merges network communication functionality with storage functionality by implementing the ESB infrastructure on shared storage. This combination allows messages to be both transmitted across networks and persisted in storage, eliminating the transient nature of traditional SOA sessions while maintaining communication flexibility.
4Reliability
If duplicate hardware components are deployed to address hardware failures, then reliability is improved, but device complexity and cost increase
Solution Approach 1:
The shared storage system creates virtual copies of data and services through its distributed architecture. Multiple instances of the same service can be deployed on different storage nodes, and the system automatically handles failover without requiring duplicate hardware components. This copying approach maintains reliability while reducing physical hardware complexity.
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
Shared storage architectures and methods are provided. A particular shared storage architecture is a system including shared storage including data and file system metadata separated from the data. The file system metadata includes location data specifying storage location information related to the data. Services are provided from service providers to service consumers through the shared storage.