Analytic model execution engine with instrumentation for granular performance analysis for metrics and diagnostics for troubleshooting

1. A system, comprising:

a processor configured to:

receive, at an interface of the system, an analytic model for processing an input data stream;

inspect the analytic model to determine a programming language of the analytic model, an action to be performed on the input data stream, a type of the input data stream, and a type of an output data stream;

generate a virtualized execution environment (VEE) for an analytic engine, wherein the VEE includes executable code to implement the analytic model for processing the input data stream, wherein the VEE binds the analytic model and a stream configuration descriptor based on a schema shared by the analytic model and the stream configuration descriptor;

translate the determined programming language of the analytic model to a first analytic model programming language, wherein the translation generates the executable code; and

route, based on the first analytic model programming language, the executable code to one runtime engine of a plurality of runtime engines of the VEE, wherein the VEE binds the analytic model with a model runner associated with the one runtime engine, wherein the one runtime engine supports the first analytic model programming language, and wherein the one runtime engine executes the executable code; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system recited in claim 1 , wherein the analytic model is implemented using a container to provide the virtualized execution environment for the analytic engine.

3. The system recited in claim 1 , wherein the analytic model is implemented using a container to provide the virtualized execution environment for the analytic engine, and wherein the container is a portable and independently executable microservice.

4. The system recited in claim 1 , wherein the analytic model includes an input configuration schema that specifies the type of the input data stream, an output configuration schema that specifies the type of the output data stream, and an I/O descriptor abstraction that specifies a stream type.

5. The system recited in claim 1 , wherein the virtualized execution environment for the analytic engine includes the plurality of runtime engines that each supports a distinct analytic model programming language.

6. The system recited in claim 1 , wherein the analytic model includes an input configuration schema that specifies the type of the input data stream, an output configuration schema that specifies the type of the output data stream, and the stream configuration descriptor that specifies a stream type, and wherein the processor is further configured to:

bind the analytic model and the stream configuration descriptor;

receive the input data stream at a stream processor;

process the input data stream using the executable code that implements the analytic model, wherein the stream processor enforces the type of the input data stream; and

generate the output data stream using the stream processor based on the type of the output data stream, wherein the output data stream includes a score and/or a metric.

7. The system recited in claim 1 , wherein the interface for receiving the analytic model for processing data includes an Application Programming Interface (API), a Command Line Interface (CLI), and/or a dashboard interface.

8. The system recited in claim 1 , wherein the processor is further configured to:

add a sensor to instrument the virtualized execution environment for the analytic engine, wherein the sensor provides metrics for monitoring, testing, statistically analyzing, and/or debugging a performance of the analytic model.

9. The system recited in claim 1 , wherein the processor is further configured to:

inspect the analytic model to determine code points for one or more of the following: state initialization, concurrency controls, state management, safety and reliability controls, beginning and end of model execution framework for input and output of data, and post-execution clean-up.

10. A method, comprising:

receiving, at an interface of a system, an analytic model for processing an input data stream;

inspecting the analytic model to determine a programming language of the analytic model, an action to be performed on the input data stream, a type of the input data stream, and a type of an output data stream;

generating a virtualized execution environment (VEE) for an analytic engine, wherein the VEE includes executable code to implement the analytic model for processing the input data stream, wherein the VEE binds the analytic model and a stream configuration descriptor based on a schema shared by the analytic model and the stream configuration descriptor;

translating the determined programming language of the analytic model to a first analytic model programming language, wherein the translation generates the executable code; and

routing, based on the first analytic model programming language, the executable code to one runtime engine of a plurality of runtime engines of the VEE, wherein the VEE binds the analytic model with a model runner associated with the one runtime engine, wherein the one runtime engine supports the first analytic model programming language, and wherein the one runtime engine executes the executable code.

11. The method of claim 10 , wherein the analytic model is implemented using a container to provide the virtualized execution environment for the analytic engine.

12. The method of claim 10 , wherein the analytic model is implemented using a container to provide the virtualized execution environment for the analytic engine, and wherein the container is a portable and independently executable microservice.

13. The method of claim 10 , wherein the analytic model includes an input configuration schema that specifies the type of the input data stream, an output configuration schema that specifies the type of the output data stream, and the stream configuration descriptor that specifies a stream type.

14. The method of claim 10 , wherein the virtualized execution environment for the analytic engine includes the plurality of runtime engines that each supports a distinct analytic model language.

15. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving, at an interface of a system, an analytic model for processing an input data stream;

inspecting the analytic model to determine a programming language of the analytic model, an action to be performed on the input data stream, a type of the input data stream, and a type of an output data stream;

generating a virtualized execution environment (VEE) for an analytic engine, wherein the VEE includes executable code to implement the analytic model for processing the input data stream, wherein the VEE binds the analytic model and a stream configuration descriptor based on a schema shared by the analytic model and the stream configuration descriptor;

translating the determined programming language of the analytic model to a first analytic model programming language, wherein the translation generates the executable code; and

routing, based on the first analytic model programming language, the executable code to one runtime engine of a plurality of runtime engines of the VEE, wherein the VEE binds the analytic model with a model runner associated with the one runtime engine, wherein the one runtime engine supports the first analytic model programming language, and wherein the one runtime engine executes the executable code.

16. The computer program product recited in claim 15 , wherein the analytic model is implemented using a container to provide the virtualized execution environment for the analytic engine.

17. The computer program product recited in claim 15 , wherein the analytic model is implemented using a container to provide the virtualized execution environment for the analytic engine, and wherein the container is a portable and independently executable microservice.

18. The computer program product recited in claim 15 , wherein the analytic model includes an input configuration schema that specifies the type of the input data stream, an output configuration schema that specifies the type of the output data stream, and the stream configuration descriptor that specifies a stream type.

19. The computer program product recited in claim 15 , wherein the virtualized execution environment for the analytic engine includes the plurality of runtime engines that each supports a distinct analytic model language.