Skip to content
actor-ts

DistributedDataSettings

Defined in: src/crdt/DistributedData.ts:203

Properties

Section titled “Properties”

durableStore?

Section titled “durableStore?”

readonly optional durableStore?: DurableStateStore

Defined in: src/crdt/DistributedData.ts:221

Optional durable backend. When provided, the local CRDT view is loaded from the store on preStart and re-saved after every mutation (local update, gossip merge, delete). Without this, DistributedData is purely in-memory — a full cluster restart (deploy / outage) starts every replica empty.

The store is keyed by replica id, so each cluster member owns its own durable record. CRDT semantics handle convergence across replicas via gossip — durability is per-replica.

Plug in any of the existing DurableStateStore implementations: InMemoryDurableStateStore for tests, the SQLite / Cassandra / S3 / filesystem backends for production.

gossipIntervalMs?

Section titled “gossipIntervalMs?”

readonly optional gossipIntervalMs?: number

Defined in: src/crdt/DistributedData.ts:205

Period between gossip pushes. Default: 1 s.