This documentation is for an unreleased version of Apache Flink Stateful Functions. We recommend you use the latest stable version.
Logical Functions #
Stateful Function’s are allocated logically, which means the system can support an unbounded number of instances with a finite amount of resources. Logical instances do not use CPU, memory, or threads when not actively being invoked, so there is no theoretical upper limit on the number of instances that can be created. Users are encouraged to model their applications as granularly as possible, based on what makes the most sense for their application, instead of designing applications around resource constraints.
Function Address #
In a local environment, the address of an object is the same as a reference to it.
But in a Stateful Functions application, function instances are virtual and their runtime location is not exposed to the user.
Address is used to reference a specific stateful function in the system.
An address consists of two components, a
A function type is similar to a class in an object-oriented language; it declares what sort of function the address references.
The ID is a primary key, which scopes the function call to a specific instance of the function type.
When a function is invoked, all actions - including reads and writes of persisted states - are scoped to the current address.
For example, imagine there was a Stateful Functions application to track the inventory of a warehouse.
One possible implementation could include an
Inventory function that tracks the number units in stock for a particular item; this would be the function type.
There would then be one logical instance of this type for each stock-keeping unit (SKU) the warehouse manages.
If it were clothing, there might be an instance for shirts and another for pants; “shirt” and “pant” would be two IDs.
Each instance may be interacted with and messaged independently.
The application is free to create as many instances as there are types of items in inventory.
Function Lifecycle #
Logical functions are neither created nor destroyed, but always exist throughout the lifetime of an application. When an application starts, each parallel worker of the framework will create one physical object per function type. This object will be used to execute all logical instances of that type that are run by that particular worker. The first time a message is sent to an address, it will be as if that instance had always existed with its persisted states being empty.
Clearing all persisted states of a type is the same as destroying it. If an instance has no state and is not actively running, then it occupies no CPU, no threads, and no memory.
An instance with data stored in one or more of its persisted values only occupies the resources necessary to store that data. State storage is managed by the Apache Flink runtime and stored in the configured state backend.