Skip to main content

Glossary

Component#

Component is an implementation of a node. Once used in a scenario, component becomes a node.

There are different types of components, each performing a different type of processing. An example of a basic component would be a filter, which filters only those records which match certain criteria. An example of a complex component would be a session window, which can perform aggregations in a session window.

For more information about the available components check Visual Processing with Nussknacker.

Deployment Manager#

Part of Nussknacker Designer working together with Executor on the deployment of the scenario to the engine where the scenarios are processed.

Engine#

Domain specific platform, where scenarios authored with Nussknacker Designer are processed. Flink is one of the engines used by Nussknacker.

Executor#

Executor implements engine specific logic to deploy a scenario to the engine.

Model#

Nussknacker is a highly configurable tool, it can work with different engines, multiple instances of the same engine, multiple components configurations. Term model is used to integrate all the 'moving parts' which work behind the scenes of the scenario. Model is comprised of:

  • components and extensions source code
  • expressions language configuration
  • listeners
  • error handling code
  • scenarios validation code used by the Designer

Node#

When a component is applied to a scenario it becomes a node; nodes are are the building blocks f a scenario.

Almost all nodes take parameters; for example a filter node takes a boolean expression as a parameter, this expression is evaluated at runtime to decide whether a given event should pass the filter node.

Nussknacker Designer#

Part of Nussknacker where authoring of scenarios is performed.

Scenario#

Scenario defines how streams of data should be processed. Scenarios are authored by means of Nussknacker Designer. Scenarios are composed of nodes.