Microservice Registry Mediates Code Execution in Isolated Guests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Isolated guests, such as virtual machines and containers, often lack essential components, leading to deficiencies in handling atypical requests to execute code, which can result in security risks and inefficiencies, especially when attempting to launch additional containers requiring elevated rights.
Innovation Solution
A microservice registry is used to manage and forward requests for executable code that is unavailable within an isolated guest, leveraging microservices to execute the code, thereby maintaining security and efficiency by utilizing a centralized service for commonly used executables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If isolated guests are designed to be lean with only necessary components, then launch latency is reduced and compute efficiency is improved, but the isolated guests lack essential components for handling atypical code execution requests
Solution Approach 1:
The patent introduces a host system as an intermediary between the isolated guest and the code execution functionality. When the isolated guest encounters unavailable executable code, it forwards the request to the host system, which retrieves and executes the code from a repository, then returns the results to the isolated guest. This mediator approach allows the lean isolated guest to access additional functionality without carrying unnecessary components.
2Adaptability or versatility
If isolated guests include all necessary components for handling any code execution scenario, then adaptability is improved, but the isolated guests become bloated and launch latency increases
Solution Approach 1:
The system segments the code execution functionality into two parts: essential components remain within the isolated guest for common operations, while non-essential or atypical executable code is separated and stored externally in a repository. This segmentation allows the isolated guest to remain lean while still accessing additional functionality when needed through the host system.
3Adaptability or versatility
If additional containers are launched to handle code execution, then code execution capability is improved, but security risks increase and lifecycle costs rise
Solution Approach 1:
The host system serves as a secure intermediary that manages code retrieval and execution from a controlled repository. Instead of allowing isolated guests to launch additional containers with elevated rights, the host system mediates the process by fetching code, executing it in a controlled environment, and returning results. This eliminates the need for isolated guests to have elevated privileges or launch additional containers, thereby reducing security risks.
4Adaptability or versatility
If isolated guests are given elevated rights to launch additional containers, then code execution capability is improved, but security risks and lifecycle costs increase
Solution Approach 1:
The isolated guest maintains self-service capability by handling common code execution requests independently using its built-in components. For atypical requests, it delegates to the host system through standardized interfaces. This self-service approach eliminates the need for elevated rights or additional containers, maintaining system security while preserving adaptability for both common and atypical scenarios.
Data Source
AI summary
Methods and systems for executing code referenced from a microservice registry are disclosed. For example, a microservice registry is stored in a memory. The microservice registry includes references to a plurality of microservices including a first microservice. An isolated guest executing on one or more processors receives a request to execute an executable code and determines that the executable code is unavailable in the first isolated guest. The isolated guest determines that, based on the microservice registry, the first microservice executes the executable code. The isolated guest forwards the first request to the first microservice and receives a result of the request from the first micro service.