Nussknacker was created as GUI for Flink. However, it's also possible to use it to connect to other runtimes.
DeploymentManagerProvider interfaces were created to facilitate this.
In particular, we provide experimental standalone engine, which allows using Nussknacker as method of creating REST APIs
To create/customize Nussknacker engine you have to:
DeploymentManagerProviderinterface and register it with ServiceLoader mechanism. Each provider should have unique
- Put implementation with all needed libraries on Nussknacker classpath.
- Configure appropriate model to use your process manager.
To configure process category to use particular engine, see following configuration:
type: ... //name of engine, e.g. "flinkStreaming"
//... - additional engine config (e.g. location of Flink cluster, etc.)
Main processing engine for Nussknacker. It's published in
Name of engine is
This engine is considered experimental. It allows to use Nussknacker to expose REST APIs or use it as
embedded rules engine. We provide simplistic implementation of process manager in
module. Name of engine is