What it does
The engine library contains a first slice of an object-storage-native log. Sealed segments are shipped to an object store as atomic uploads and a cold boot can rebuild the log from the store. The server cannot select it, and the slice supports a local filesystem URL and nothing more, so it is not available to users.
How it works
The object backend wraps the ordinary local log. The on-disk segments act as a write-through cache, and each sealed, immutable segment is uploaded as one object whose key carries a prefix and the zero-padded first sequence number. The object is a byte-identical copy of the segment file. On open, the backend lists the store, downloads any segment objects missing locally and then opens the inner log for replay, so wiping the local log directory and reopening against the same store brings every record back. A checkpoint-derived floor lets boot skip segments entirely below it.
Uploads are queued from the log's seal hook and drained as a barrier on flush and sync. Trimming local segments waits for their uploads. A truncated object in the store is not trusted as uploaded.
Slice 1 accepts file:// URLs, backed by a local filesystem store, and nothing else. There are no cloud stores, no checkpoints in the store, and no deletion of store objects when the log is truncated.
The storage choice in the server is `file` or `postgres`. Any other value of KYNETRA_STORAGE_BACKEND is not recognised and the server starts with the file log. A Cloudflare D1 durability backend is not part of this edition's engine and is a roadmap item.
Where you reach it
- Library
EngineConfig::storage(StorageKind::Object { url: "file:///…", prefix }) (engine library, not wired to the server)
Limits
- Not reachable from the server or the command line. Setting KYNETRA_STORAGE_BACKEND to object does not select it.
- A file:// URL is the sole supported form. No S3, GCS or Azure store is implemented.
- Truncating or restoring the log does not remove objects from the store.
- No performance or durability figure exists for this backend.
Evidence
- TestsCovered in the engine repository by 7 backend tests (byte-identical upload, cold boot from the store alone, upload barrier before local trim, replay floor, truncated object not trusted) and 2 storage-location tests
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
This is not available in the preview. Request a preview to discuss the current scope.