Model lifecycle management
An example computer system for implementing a lifecycle of a model can include: one or more processors; and non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to create: an orchestration service programmed to create a workflow for model execution; and a registration service programmed to provide governance for the workflow; wherein the orchestration service and the registration service are microservices, and the microservices communicate programmatically to facilitate the model execution.
1 . A computer system for implementing a lifecycle of a model, comprising:
one or more processors; and
non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, causes the computer system to create:
an orchestration service programmed to create a workflow for model execution;
a registration service programmed to provide governance for the workflow, wherein the registration service is further programmed to register deployed models on the computer system and provide data and model dependencies across the computer system;
a validation service programmed to provide a sandbox for model generation, wherein the sandbox is segregated from a remainder of the computer system and allows for isolation during validation of the model, wherein the sandbox provides for execution of scripting to allow for creation and deployment of the lifecycle of the model, and wherein the validation service provides isolated containers and remote model execution for the isolation during validation; and
an interface service programmed to:
function as a model-as-a-service through an application programming interface, wherein the interface service provides a common abstract interface for models, and wherein the interface service allows for external systems to make requests for the model execution and receive outputs from the model execution through the application programming interface; and
provide an interface upon which the workflow is developed, wherein the interface includes a component palette listing a plurality of components, and a canvas upon which one or more of the plurality of components is arrangeable to create the workflow, and wherein the one or more of the plurality of components is draggable from the component palette to the canvas to create the workflow;
wherein the orchestration service, the registration service, the validation service, and the interface service are microservices, and the microservices communicate programmatically to facilitate the model execution.
2 . The computer system of claim 1 , wherein each of the orchestration service and the registration service is further programmed to publish events in a publish/subscribe system.
3 . The computer system of claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to create an exchange service programmed to provide auditing and traceability for the model.
4 . The computer system of claim 1 , comprising further instructions which, when executed by the one or more processors, causes the computer system to create a track service programmed to provide model telemetry to allow for monitoring of the model.
5 . The computer system of claim 1 , wherein the registration service is further programmed to manage documentation and changelog information for the model.
6 . A method for implementing a lifecycle of a model, the method comprising:
creating a workflow for model execution;
providing governance for the workflow, including registering deployed models on a computer system and providing data and model dependencies across the computer system; and
providing a sandbox for model generation, wherein the sandbox is segregated from a remainder of the computer system and allows for isolation during validation of the model, wherein the sandbox provides for execution of scripting to allow for creation and deployment of the lifecycle of the model, and wherein isolated containers and remote model execution are provided for the isolation during validation;
providing an interface service programmed to:
function as a model-as-a-service through an application programming interface, wherein the interface service provides a common abstract interface for models, and wherein the interface service allows for external systems to make requests for the model execution and receive outputs from the model execution through the application programming interface; and
provide an interface upon which the workflow is developed, wherein the interface includes a component palette listing a plurality of components, and a canvas upon which one or more of the plurality of components is arrangeable to create the workflow, and wherein the one or more of the plurality of components is draggable from the component palette to the canvas to create the workflow;
wherein the workflow, the governance, and the interface are embedded in microservices, and the microservices communicate programmatically to facilitate the model execution.
7 . The method of claim 6 , further comprising publishing events in a publish/subscribe system for the microservices.
8 . The method of claim 6 , further comprising providing auditing and traceability for the model.
9 . The method of claim 6 , further comprising providing model telemetry to allow for monitoring of the model.
10 . The method of claim 6 , further comprising managing documentation and changelog information for the model.