Component · built
It forgets everything, on purpose.
The realtime layer moves topic messages between nodes and never once reaches for a disk. If persistence is off — and it is, by default — there is no storage code in the path to accidentally trigger. Fast because there's nothing else in the way.
What's built
- Topic-based publish/subscribe over the authenticated mesh links
- Runs entirely on the mutual-TLS transport — no separate auth to configure
- Message IDs minted from a CSPRNG; the broker refuses to start if it can't
- On by default; a node needs no flags to participate in streaming
What it deliberately isn't
- A queue. Nothing is retained; a subscriber that wasn't listening missed it.
- A database with a stream bolted on. The stream is the product.
- At-least-once. Delivery is best-effort by design — turn on shard storage if you need a record.
If you want "streaming, but also keep it," that's the shard store's job, and you opt into it per node.