@xemahq/biome-database-nest

Explicit database ownership and runtime wiring for Xema biomes

Overview

Gives a Xema biome service explicit database ownership without coupling it to a deployment environment. It supplies schema-qualified Prisma wiring, validates image/schema compatibility, and provides a governed lifecycle for data cutovers that require an operator between expansion and contraction.

When to use it

• Use it when a NestJS biome service stores data or owns database migrations.
• Use its operator lifecycle when a destructive contraction must wait for a verified backfill instead of running automatically at application startup.
• Wrap the complete operator command with withOperatorMigrationLock so apply, verification, and contraction cannot overlap across replicas.

Installation

pnpm add @xemahq/biome-database-nest

Usage

import {
  BiomeDatabaseMigrationMode,
  BiomeDatabaseModule,
} from '@xemahq/biome-database-nest';

BiomeDatabaseModule.forRoot({
  biomeId: 'example',
  migrationMode: BiomeDatabaseMigrationMode.ApplicationManaged,
  databases: [{ workspaceDir: process.cwd() }],
});

Peer requirements

• NestJS 10 or 11 and Prisma 7.
• Compatible Xema identity, kernel-contract, service-registry, and decorator packages.

License

Apache-2.0 © Xema — xema.dev