Hybrid Runtime Bridging for Cross-Environment File Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developers face significant time and resource consumption when rebuilding and porting previously developed code to run in a different runtime environment, increasing development costs.
Innovation Solution
A hybrid runtime environment system enables cross-environment execution by wrapping a source code file in a wrapper based on metadata, exposing it as an HTTP endpoint, and passing arguments to a second virtual machine to execute the code, reducing the need for rebuilding and porting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If previously developed code is rebuilt and ported to a different runtime environment, then the code can run in the new environment, but substantial time and resources are consumed
Solution Approach 1:
The patent introduces a hybrid runtime environment that acts as an intermediary between the original runtime environment and the new runtime environment. This hybrid runtime contains both the original runtime environment (to execute the previously developed code) and the new runtime environment (to provide compatibility with the target system), allowing code to run in the new environment without rebuilding or porting
Solution Approach 2:
The hybrid runtime environment is designed to support multiple runtime environments simultaneously, making it universal. It can execute code from different runtime environments within the same system, eliminating the need to rebuild code for each specific environment and enabling direct execution of previously developed code in new environments
2Adaptability or versatility
If previously developed code is rebuilt and ported to a different runtime environment, then the code can run in the new environment, but resources and costs increase
Solution Approach 1:
The hybrid runtime environment serves as a mediator that eliminates the need for resource-intensive rebuilding and porting processes. By providing both runtime environments in one system, it allows direct execution of code without the costly and time-consuming traditional workflow of rebuilding and porting
Solution Approach 2:
The hybrid runtime environment is pre-configured with both the original and new runtime environments before code execution is needed. This preliminary setup eliminates the need for reactive rebuilding and porting operations, allowing code to be executed directly in the new environment without additional resource consumption
Data Source
AI summary
Techniques are described herein that are capable of performing cross-environment execution of a file in a hybrid runtime environment. A first virtual machine (VM) corresponding to a first managed runtime environment (MRE) is caused to load bridging logic by loading the first VM. The bridging logic loads a second VM corresponding to a second MRE. The first VM converts a source code file, which is created from metadata associated with a file in the second MRE, into a compiled file, which corresponds to the first MRE, and exposes the compiled file as an HTTP endpoint. The first VM passes an argument, which is included in a call from the HTTP endpoint, to the second VM via the bridging logic, which causes the second VM to generate a result by executing the file using the argument. The first virtual machine provides the result to the HTTP endpoint.