Skip to main content

Module backends

Module backends 

Source
Expand description

Backend-selection enums for a node’s blob + KV stores (node-library N2b).

These are the domain types the store-construction assembly dispatches on. They live here (not the binary) so the assembly can move into the library; the clap::ValueEnum derive is behind the optional clap feature so the CLI binary uses them directly in its args, while a non-CLI embedder never pulls clap. (build_kv/build_blobs join this module as they migrate off the binary’s ServeArgs.)

Structs§

SlateKvS3
Where the SlateDB control-plane store lives when it runs on an S3-compatible object store (Cloudflare R2) instead of local disk — the durable, remote-state deployment. Credentials come from the ambient AWS environment (AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY), matching the S3 blob backend.

Enums§

BlobBackend
Blob (file-content) backend.
KvBackend
Metadata (manifest + pointer) backend.

Constants§

CONTROL_PLANE_FLUSH
Flush interval for the control-plane SlateDB store: tiny, so a control-plane write is durable almost immediately (correctness over throughput).

Functions§

build_kv
Build the metadata KV store for the selected KvBackend. When slate_s3 is set (and the backend is SlateDB), the store runs on R2/S3 (durable across a scale-to-zero container stop) rather than the local data_dir.