Data Grid Routing via Intermediary Server in Computing Clusters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cluster computing environments, existing routing systems for data grids face inefficiencies due to the need for re-routing requests through non-owner nodes, leading to performance issues and resource waste, especially when dealing with large numbers of nodes.
Innovation Solution
Implementing a server-based routing system that maintains and updates data grid topology dynamically, using a proxy component to route requests directly to the correct owner node without exposing all nodes externally, thereby minimizing network resource usage and security risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a traditional routing system is used where all nodes are exposed externally, then clients can access any node directly, but network resource usage increases and security risks increase due to unnecessary data transmission through non-owner nodes
Solution Approach 1:
The patent introduces a server as an intermediary component that maintains the data grid topology and routes client requests to the correct owner nodes. This mediator server receives requests from clients, determines the appropriate destination node using the maintained topology information, and forwards requests only to necessary owner nodes, thereby eliminating wasteful network traffic through non-owner nodes while improving routing efficiency
2Adaptability or versatility
If all nodes are exposed externally for direct access, then clients have full access to the data grid, but security risks increase due to unnecessary exposure of node information
Solution Approach 1:
The server acts as a security intermediary that maintains topology information without exposing all node details to clients. The server receives requests, uses the maintained topology to determine appropriate destinations, and forwards requests selectively, thereby providing necessary accessibility while minimizing security risks by not exposing the complete node structure to external clients
Solution Approach 2:
The patent extracts the topology maintenance and routing functionality from the client-side application and centralizes it on the server side. This extraction allows the server to manage topology information securely without requiring clients to have direct access to or knowledge of the complete node structure, thereby reducing security risks while maintaining accessibility
3Ease of operation
If clients handle topology information directly, then routing decisions can be made at the client side, but complexity increases as clients must manage topology updates and consistency
Solution Approach 1:
The server serves as an intermediary that maintains the data grid topology centrally and handles all routing decisions. Clients simply interact with the server, which uses the maintained topology information to determine appropriate destination nodes. This approach simplifies client operations while the server manages the complexity of topology updates and consistency
Solution Approach 2:
The patent extracts topology management responsibilities from clients and centralizes them on the server. The server maintains topology information and handles routing decisions, freeing clients from the complexity of managing topology updates and consistency while maintaining ease of operation for clients
Data Source
AI summary
A method includes receiving a description of a data grid topology of a containerized computing cluster, wherein the containerized computing cluster comprises a plurality of nodes that are divided into a plurality of partitions and each partition of the plurality of partitions is identified by a respective partition number, and the data grid topology maps the respective partition number to an address of corresponding nodes for the respective partition; labeling each pod with a partition number according to the data gird topology, wherein each pod comprises one or more virtualized computing entities running on one or more host computer systems, wherein each pod corresponds to a node of the plurality of nodes; creating a routing service for each partition number, wherein the routing service comprises an application programmer interface (API) object identifying at least one pod; and creating a routing API object to route a request to the routing service.