Skip to content
Browse documentation
typescript sdk

Redis queues

Use explicit scoped Redis transport while retaining run persistence and host ownership.

Compose paired queue owners

import {
  RedisDispatchQueue,
  RedisWorkerQueue,
} from "@smoothie-framework/worker-redis";

Configure paired queues with the same executionScope tenant/project and consumerId. Runtime and dispatcher construction reject mismatched scopes. Install the compatible redis peer when using the default client.

One active dispatch queue owns each key set. Distinct consumer identities need independently scoped keys. This adapter does not supply a distributed active/passive ownership lease.

Keep transport separate from durable history

Command claims and acknowledgments recover unacknowledged messages with stable processing identity. Durable projection consumers are awaited before acknowledgment; ordinary observer callbacks remain best-effort.

Retained result/event lists are bounded. Monitor listener errors and queue depth so projection failure or backpressure is visible. Do not use retained queue data as the source of truth after restart.

Compose durable stores and a projector as described in Persistence, controls and recovery. Redis availability alone does not make a run durable.