Service Mesh Parameter Optimization via Tokenization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Microservices architecture in service meshes leads to unnecessary resource usage and increased data transfer costs due to the passing of large amounts of parameter data between services, which can be financially costly and affect performance.
Innovation Solution
Implementing a Request Parameter Store (RPS) that tokenizes data in service requests, allowing only services that utilize the data to retrieve it from the store, reducing unnecessary data transfer and optimizing resource usage by pre-populating caches for frequently accessed data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If large amounts of parameter data are passed between microservices, then services can access required data, but network usage and data transfer costs increase
Solution Approach 1:
The patent extracts large parameter data from service request transmissions and stores it in a centralized request parameter store. Only small unique tokens are transmitted between services, while the actual large data remains stored centrally. This resolves the contradiction by maintaining data accessibility through the store while dramatically reducing network usage through token-based reference passing.
Solution Approach 2:
The request parameter store acts as an intermediary between microservices, allowing services to access large parameter data without directly transmitting it. Services retrieve data through the intermediary store using tokens, which eliminates the need for direct large-data transmission between services while maintaining full data accessibility.
2Reliability
If large amounts of parameter data are passed between microservices, then services can access required data, but memory usage and CPU usage increase
Solution Approach 1:
The patent extracts large parameter data from service memory spaces and stores it in a centralized request parameter store. Services only hold small tokens in memory rather than large data structures, dramatically reducing memory usage while maintaining data accessibility through the centralized store.
Solution Approach 2:
Instead of copying large parameter data between service memory spaces, the patent uses token copies that reference the original data in the centralized store. This allows multiple services to access the same data without duplicating it in memory, reducing overall memory consumption while maintaining accessibility.
3Adaptability or versatility
If parameter data is passed through multiple microservices, then data can reach downstream services, but data transfer costs increase
Solution Approach 1:
The patent extracts large parameter data from transmission streams and stores it centrally. Only small tokens are transmitted through the service mesh, reducing data transfer costs by orders of magnitude while maintaining the ability to route data to any downstream service that needs it.
Solution Approach 2:
The request parameter store serves as an intermediary that enables data routing without data transmission. Services request data through the intermediary using tokens, and the intermediary retrieves and delivers only the necessary data portions, eliminating unnecessary data transfer costs while maintaining routing flexibility.
4Adaptability or versatility
If all parameter data is transmitted to each service, then services have all available data, but unnecessary resource usage increases
Solution Approach 1:
The patent implements local quality by allowing services to access only the specific parameter data they need from the centralized store, rather than receiving all parameter data. Each service retrieves data locally from the store based on its specific requirements, improving resource efficiency while maintaining data availability for all services that need it.
Data Source
AI summary
A computer-implemented method, apparatus, system and computer program product for optimizing parameter data passing between services in a service mesh, the method including receiving, at a first service, a request for the first service, the request including parameter data; storing the parameter data in a request parameter store, retrieving the parameter data from the request parameter store; the first service initiating a request for a second service, the parameter data in the request being replaced by a unique token identifying the parameter data in the request parameter store; and responsive to the second service using the parameter data, retrieving the parameter data from the request parameter store.