Nereus documentation
Nereus is a shared stream storage layer beneath Pulsar and Native Kafka. Protocol brokers retain their protocol semantics; Nereus owns durable bytes, logical offsets, committed heads, physical generations, recovery, and safe reclamation.
This site follows the dependency order of the architecture model. Read the overview first, then move through logical coordinates, WAL and commit, write/read paths, integrations, and operations.
Documentation source
The initial migration is grounded in the local architecture snapshot Nereus 当前架构与端到端流程, generated from nereusstream/nereus main@894fc4e4. The page baseline is separately checked against the current Nereus main@c820391d on 2026-08-07. The document baseline explains this distinction and the coverage map.
Start here
- Why Nereus? — the boundary between protocol semantics and storage semantics.
- Architecture — the layers, authorities, and source anchors.
- Stream, record, entry, and offset — the coordinate model used by every adapter.
- Current migration status — what has been verified and what remains to migrate.