Persistence

DSAR uses persistence drivers to store request state, audit events, policy assignments, and all other domain records in a database. Each driver implements the same PersistenceDriver contract, so you can swap databases without changing application code.

Available Drivers

How Persistence Works

The persistence layer is tenant-scoped — every database operation runs within a tenant context. The withTenant helper scopes Effect programs to a specific tenant:

import { Persistence, withTenant } from "@dsar/persistence";
import { Effect } from "effect";

const program = Persistence.pipe(
	Effect.flatMap((p) => p.requests.list()),
	withTenant("tenant-1")
);

Domain Records

The persistence layer manages these record types:

Choosing a Driver

• Starting out? Use persistence-sqlite with in-memory mode for instant setup.
• Production? Use persistence-pg for Postgres with advisory-lock migration protection.

Wiring with the Backend

import { dsarInstance, runtimeReposFromPersistence } from "@dsar/backend";
import { makeSqlitePersistenceService } from "@dsar/persistence-sqlite";

const persistence = await makeSqlitePersistenceService();

const runtime = dsarInstance({
	repos: runtimeReposFromPersistence(persistence),
});

Related

• Getting Started
• Request Lifecycle
• Architecture: Tenant-Safe Persistence