Birds of a Feather Session - Stateful Functions
summary
Stateful Functions announces a shipping JavaScript/TypeScript SDK, enables a new async non-blocking transport by default, and adds user-defined metrics; remote functions run truly asynchronously, buffer inbound messages per address, and allow minute‑long computations if container timeouts are tuned. Configuration moves from a single modules YAML to decomposed, Kubernetes‑native resources. Roadmap includes dead‑letter / pubsub ideas and multi‑tenancy explorations. The hardest engineering work is designing the cross‑language API surface and semantics.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 0:46Recent developments in Stateful Functions
- 5:04Remote vs embedded functions
- 7:15Kubernetes-native direction
- 10:21Multi-tenancy considerations
- 20:14Failure handling and recovery
- 24:34Heavy remote functions and side effects
- 29:26Design challenges in Stateful Functions
- 31:38Future features and direction
- 33:47Comparison with AWS Step Functions
- 37:43Closing remarks and next steps
related talks
27mStateful Functions 3.0: Towards a Cross-Platform Stateful Serverless Stack
55mStateful Functions: Polyglot Event-Driven Functions for Stateful Distributed Applications
34mHands-on Stateful Serverless Applications with Kubernetes and Stateful Functions
38mDeploying Stateful FaaS on Streaming Dataflows
42mInterview and AMA with the creators of Stateful Functions
38mState is Hard: An SDK for Building Stateful Applications
25mElastic Scaling of Stateful Network Functions
34mModule Federation, Bundlers, and Future State