Bridging the CHASM @ Replay 2026 | A Deep Dive Into Temporal's Server's State Machine SDK
summary
Temporal’s internal CHASM server-side state-machine SDK provides concrete abstractions — components, fields, archetypes, tasks — and an outbox-style task model with a state-based replication (ver/transition) protocol. Developers built an updatable-timer component, extended the server gRPC API (start/update/describe/list/wait/terminate), and demoed LLM-assisted code generation that started a timer, updated its deadline, and observed it fire. CHASM adds pure-task collapsing, per-component ver tracking for replication, and already hosts standalone activities, a scheduler rewrite, and a full Nexus port started late 2025.
AI-written summary · about
chapters (10)
- 0:00Introduction to Chasm
- 5:28Demo of updatable timer
- 10:32Chasm components and executions
- 14:26Task processing in Chasm
- 22:10RPC processing in Temporal
- 25:48Visibility in Chasm
- 31:44Replication protocol overview
- 37:02State-based replication
- 39:09Future work and migration plans
- 42:18Q&A and closing remarks
related talks
12mWrite durable and resilient workflows in Swift
40mAn Interdisciplinary View on Prototypes - Towards Executable Models That Can Be...
21mDDD and FSM: tackling complexity with state machines
27mSupercharging Backstage Scaffolder for Workflows
51mMicroProcess Architectures: Planning for Change, & Retaining Flexibility
15mAbstract Interpretation of Temporal Safety Effects of Higher Order Programs
24mArchitecting the Unconventional: A Case Study in Software Design
47mBEAM Architecture Handbook