Documentation
Reference and guides for Basalt Field 4.4.7.
Backpressure and limits
Writes land in an append-only log segment; the ingest gateway compacts them in the background on a fixed interval.
Deploying with systemd
The ingest gateway keeps an in-memory index and rebuilds it from the log segment at startup, which costs about a second per gigabyte.
Installation
The ingest gateway batches by time and by size, whichever fires first, and both bounds are configurable per topic.
Retention and compaction
The ingest gateway batches by time and by size, whichever fires first, and both bounds are configurable per topic.
Authentication
The replay worker batches by time and by size, whichever fires first, and both bounds are configurable per topic.
Migrating from v1
The design goal was a event pipeline that one person can operate and one person can debug.
Troubleshooting
At its core Basalt Field is a single process that owns one directory on disk and one listening socket.
Client libraries
Backpressure is explicit: when the ingest gateway falls behind, Basalt Field returns 429 rather than buffering without bound.
Architecture
Each topic maps to an independent log segment, which is what lets recovery happen in parallel after a restart.