Glossary of internal terms

This page complements the Glossary, which defines the user-facing terms (scenario, component, node, processing mode, engine, deployment target, ...). The terms below describe how Nussknacker is built and are needed to read and write its code and developer documentation.

Deployment Manager

Code that deploys a scenario (submits it for execution), checks the scenario's state, and so on, for example FlinkDeploymentManager, K8sDeploymentManager or EmbeddedDeploymentManager. It runs in Designer and communicates with the Executor.

A deployment target is configured in a scenario type's deploymentConfig and names the type of Deployment Manager that serves it, together with that Deployment Manager's configuration. The deployment target is the user-facing destination; the Deployment Manager is the code that deploys to it. Older code and documentation called it a process manager (FlinkProcessManager, StandaloneProcessManager).

Executor

Software on the engine side, in the strict sense of the word, responsible for the execution of a scenario by the engine (the Flink case, for example the job built by FlinkScenarioJob and FlinkProcessRegistrar), or the implementation of the engine itself (the Lite case, for example RequestResponseScenarioInterpreter).