Stateful Functions applications are composed of one or more modules. A module is a bundle of functions loaded by the runtime and made available to be messaged. Functions from all loaded modules are multiplexed and free to message each other arbitrarily.
Stateful Functions supports two types of modules: Remote and Embedded.
Remote modules run as external processes from the Apache Flink® runtime; in the same container, as a sidecar, using a serverless platform or other external location.
This module type can support any number of language SDKs.
Remote modules are registered with the system via
YAML configuration files.
A remote module configuration consists of a
meta section and a
meta contains auxiliary information about the module;
spec describes the functions contained within the module and defines their persisted values.
module.spec.functions declares a list of
function objects that are implemented by the remote module.
function is described via a number of properties:
http+unix://<socket-file-path>/<serve-url-path>. For example,
name property and an optional
expireAfter - 0, meaning that state expiration is disabled.
address before invoking backpressure on the system.
Embedded modules are co-located with, and embedded within, the Apache Flink® runtime.
This module type only supports JVM-based languages and is defined by implementing the
Embedded modules offer a single configuration method where stateful functions bind to the system based on their
Runtime configurations are available through the
globalConfiguration, which is the union of all configurations
in the applications
flink-conf.yaml under the prefix
statefun.module.global-config, and any command line
arguments passed in the form
Embedded modules leverage Java’s Service Provider Interfaces (SPI) for discovery.
This means that every JAR should contain a file
org.apache.flink.statefun.sdk.spi.StatefulFunctionModule in the
META_INF/services resource directory that lists all available modules that it provides.