Runtime management of application components
AssigneeBildr, Inc.
InventorsMark D. Magnuson, Timothy J. Magnuson
Life of this patent
Estimating the term…
Abstract
Techniques are described for runtime checking of function metadata prior to execution of a function in an environment. An application may include any appropriate number of components at one or more levels in a hierarchical arrangement, and each component may be packaged with metadata that describes the component. A function, or any component, may be packaged with metadata that includes term(s) governing the usage of the function. The term(s) may be checked, at runtime, during execution of the application to determine whether the function is to be executed. A function may also be hashed at runtime for verification of function version. Function(s) may be individually and independently executed as containerized nano functions within the environment.
Claims20
A computer-implemented method performed by at least one processor, the method comprising:
- presenting a configuration user interface (UI);
- receiving, in the configuration UI, an input indicating a function to be included in an application;
- automatically generating metadata for the function, the metadata for the function comprising:
- at least one term that must be met to enable execution of the function;
- and
- metadata describing the function;
- transmitting the application for execution, wherein the application comprises the metadata for the function, and execution of the application comprises:
- determining, prior to execution of the function, that the at least one term is met;
- and
- executing the function as a nano function that executes, independently of other functions, in a locally executing instance of a container that does not include another executing function.
A system comprising:
- at least one processor;
- and
- a memory communicatively coupled to the at least one processor, the memory storing instructions which, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
- presenting a configuration user interface (UI);
- receiving, in the configuration UI, an input indicating a function to be included in an application;
- automatically generating metadata for the function, the metadata for the function comprising:
- at least one term that must be met to enable execution of the function;
- and
- metadata identifying the function;
- transmitting the application for execution, wherein the application comprises the metadata for the function, and execution of the application comprises:
- determining, prior to execution of the function, that the at least one term is met;
- and
- executing the function as a nano function that executes, independently of other functions, in a locally executing instance of a container that does not include another executing function.
A non-transitory computer-readable storage medium storing software comprising instructions executable by one or more computers which, upon execution, cause the one or more computers to perform operations comprising:
- presenting a configuration user interface (UI);
- receiving, in the configuration UI, an input indicating a function to be included in an application;
- automatically generating metadata for the function, the metadata for the function comprising:
- at least one term that must be met to enable execution of the function;
- and
- metadata describing the function;
- transmitting the application for execution, wherein the application comprises the metadata for the function, and execution of the application comprises:
- determining, prior to execution of the function, that the at least one term is met;
- and
- executing the function as a nano function that executes, independently of other functions, in a locally executing instance of a container that does not include another executing function.
Dependencies are inferred from the claim text.