Service Mesh Agent Routing Application Calls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In virtual systems, applications face challenges in communicating with each other due to the need to know unique route addresses for different protocols, leading to bottlenecks at destination ports and inefficiencies in communication protocols.
Innovation Solution
An agent DNS server assigns unused IP addresses to applications, using a metadata service to retrieve route addresses and forward calls to the correct destination ports, allowing applications to communicate without needing to track each other's route addresses, thereby avoiding bottlenecks and supporting multiple protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each application knows the route address for each protocol of other applications, then communication between applications is possible, but the system complexity and burden on applications increase
Solution Approach 1:
The patent introduces a service mesh infrastructure with sidecar proxies as intermediaries between applications. These sidecars handle protocol translation and route address management, allowing applications to communicate without directly knowing route addresses for each protocol. The service mesh acts as a mediator that abstracts the complexity of multi-protocol communication.
Solution Approach 2:
The patent segments the communication infrastructure into separate components: applications, sidecar proxies, and service mesh control plane. Each component has a specific responsibility, with sidecars handling protocol-specific route address management. This segmentation allows applications to remain simple while the infrastructure handles the complexity of multi-protocol communication.
2Device complexity
If conventional systems use a single protocol with restrictions on applications, then implementation is simpler, but bottlenecks occur at destination ports receiving network traffic
Solution Approach 1:
The patent implements a universal service mesh infrastructure that supports multiple protocols (HTTP, gRPC, WebSocket, etc.) simultaneously. The sidecar proxies are designed to handle multiple protocol types and can dynamically route traffic based on the protocol being used. This multi-functional approach eliminates bottlenecks by providing dedicated handling for each protocol while maintaining a unified architecture.
Solution Approach 2:
The service mesh dynamically adapts to different protocols and traffic patterns. The sidecar proxies can dynamically create and manage route addresses based on the protocol being used, and the system can dynamically adjust routing rules based on current traffic conditions. This dynamic behavior prevents bottlenecks by flexibly allocating resources based on actual communication needs.
3Adaptability or versatility
If applications communicate using multiple protocols with unique route addresses, then protocol versatility is achieved, but the number of requests and hops increases reducing performance
Solution Approach 1:
The service mesh pre-establishes route addresses and routing rules for multiple protocols before communication occurs. When an application needs to communicate using a specific protocol, the route address is already available in the service mesh, eliminating the need for runtime discovery and reducing the number of hops. This preliminary setup of routing information accelerates communication while maintaining multi-protocol support.
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for routing communication to applications. In an embodiment, first application can transmit a connection to a second application without knowing the exact route address of the second application. An agent can intercept the connection from a first application intended for a second application. The agent can identify the route address for the second application, determine the protocol the connection was intended to be transmitted, and forward the connection based on the route address and protocol to the second application.