Static
ClientThe MemFlow Client
service is functionally
equivalent to the Temporal Client
service.
Static
ConnectionThe MemFlow Connection
service is functionally
equivalent to the Temporal Connection
service.
Static
HandleThe Handle provides methods to interact with a running workflow. This includes exporting the workflow, sending signals, and querying the state of the workflow. An instance of the Handle service is typically accessed via the MemFlow.Client class (workflow.getHandle).
Static
WorkerThe MemFlow Worker
service is functionally
equivalent to the Temporal Worker
service.
Static
didChecks if an error is a HotMesh reserved error type that indicates a workflow interruption rather than a true error condition.
Checks if an error is a HotMesh reserved error type that indicates a HotMesh interruption rather than a true error condition.
When this returns true, you can safely return rethrow the error. The workflow engine will handle the interruption automatically.
The error to check
true if the error is a HotMesh interruption
Static
workflowThe MemFlow workflow
service is functionally
equivalent to the Temporal Workflow
service
with additional methods for managing workflows,
including: execChild
, waitFor
, sleep
, etc
Static
clearStatic
registerRegister a workflow interceptor
The interceptor to register
Static
shutdown
The MemFlow service provides a Temporal-compatible workflow framework backed by Postgres. It offers durable execution, entity-based memory management, and composable workflows.
Core Features
1. Entity-Based Memory Model
Each workflow has a durable JSONB entity that serves as its memory:
2. Hook Functions & Workflow Coordination
Spawn and coordinate multiple perspectives/phases:
3. Durable Activities & Proxies
Define and execute durable activities with automatic retry:
4. Workflow Composition
Build complex workflows through composition:
5. Workflow Interceptors
Add cross-cutting concerns through interceptors that run as durable functions:
Basic Usage Example