Service Mesh Gateway for Non-Sidecar Application Proxy Injection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in enabling communication between non-sidecar applications and service meshes, as non-sidecar applications cannot easily utilize sidecar proxy functionality, requiring manual configuration that is not scalable for large-scale data centers.
Innovation Solution
The implementation of a Service Mesh Gateway (SMG) that manages a pool of proxies associated with non-sidecar applications, allowing for automatic injection of sidecar proxy functionality into non-sidecar systems, thereby facilitating communication with service meshes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If sidecar proxy functionality is injected into containerized applications, then communication with service meshes is enabled, but manual configuration is required for non-sidecar applications which reduces scalability
Solution Approach 1:
The Service Mesh Gateway acts as an intermediary between non-sidecar applications and the service mesh. It manages a pool of sidecar proxies and automatically injects them into non-sidecar applications, enabling communication without manual configuration. The gateway mediates the interaction by handling proxy lifecycle management, routing traffic, and coordinating with both the service mesh control plane and non-sidecar applications.
2Reliability
If manual configuration is used for non-sidecar applications, then proxy functionality can be implemented, but scalability is reduced for large-scale data centers
Solution Approach 1:
The Service Mesh Gateway enables self-service by automatically detecting non-sidecar applications and injecting appropriate sidecar proxies without requiring manual configuration. The system self-manages the entire process including proxy selection, injection, lifecycle management, and removal, allowing large-scale deployment across data centers while maintaining reliable proxy functionality.
3Productivity
If sidecar proxies are automatically managed, then scalability is improved, but system architecture complexity increases
Solution Approach 1:
The Service Mesh Gateway is designed as a universal component that handles multiple functions: managing the proxy pool, injecting proxies into non-sidecar applications, routing traffic, coordinating with the service mesh control plane, and managing proxy lifecycle. This multi-functional design consolidates complexity into a single gateway component rather than distributing it across multiple specialized systems.
Data Source
AI summary
Disclosed are embodiments for injecting sidecar proxy capabilities into non-sidecar applications, allowing such non-sidecar applications to communicate with a service mesh architecture. In an embodiment, a method comprises receiving a request to instantiate a proxy for a non-sidecar application at a service mesh gateway (SMG). The SMG then instantiates the proxy in response to the request and broadcasts network information of the non-sidecar application to a mesh controller deployed in a containerized environment. Finally, the SMG (via the proxy) transmits data over a control plane that is communicatively coupled to the mesh controller.