NitriteIsolate class

Runs a Nitrite database inside a dedicated owner isolate and lets any number of other isolates read and write the same database concurrently.

A file-backed store (e.g. Hive) cannot be opened by more than one isolate at once — independent in-memory state would diverge and concurrent writes would corrupt the file. NitriteIsolate solves this by keeping the database in a single owner isolate and serialising every operation through it. A handle is itself sendable (it wraps only a SendPort), so after spawn you can pass the same handle to as many client isolates as you like and they will all share one consistent database.

// open once on an owner isolate
final db = await NitriteIsolate.spawn(openMyDb); // openMyDb is top-level

// hand the (sendable) db to worker isolates; all share the same data
await Future.wait([
  Isolate.run(() async { await db.getCollection('c').insert([doc]); }),
  Isolate.run(() async { return db.getCollection('c').size; }),
]);

await db.close();

Documents, filters, find options and ids are passed by value across the isolate boundary, so results are materialised lists rather than live cursors. Typed repositories are not proxied (their converters live only in the owner) — use document collections.

Properties

Methods

Operators

Static Methods

nitrite library