Files
modules/consensus-coordination/hyper-p2p-raft-lite
Raven ScottandCursor 713a450f2f feat(consensus,routing,scheduling): manually expand coordination and path modules
- leader-lease: renew, resign, isLeader, followers, lease expiry helpers
- quorum-pool: autoResolve, cancel, listVotes, member remove, TTL proposals
- raft-lite: requestVote, stepDown, logSlice, advanceCommit
- pattern-router: middleware chain, priority routes, routeBatch
- merge-registry: bulkRegister, diff, watch, publishSnapshot, tombstones
- cron-gossip: pause, resume, forceFire, nextDue
- topic-lease: extend, conflicts, allHolders

Co-authored-by: Cursor <[email protected]>
2026-05-21 02:14:41 -04:00
..
2026-05-20 23:36:32 -04:00
2026-05-20 23:36:32 -04:00
2026-05-20 22:56:32 -04:00
2026-05-21 00:07:44 -04:00
2026-05-20 21:57:50 -04:00
2026-05-20 21:57:50 -04:00
2026-05-20 23:36:32 -04:00

hyper-p2p-raft-lite

Minimal Raft-inspired replicated log gossip: append entries, track commit index, optional leader role.

Category: Consensus & coordination · Protocol: raft-lite/v1

When to use

Ordered append-only logs across peers when you control leader promotion explicitly.

When not to use

Production BFT, snapshotting, or full Raft safety (use a complete Raft implementation or hyper-p2p-causal-consensus).

Quick start

const { HyperP2PRaftLite } = require('hyper-p2p-raft-lite')
const raft = new HyperP2PRaftLite({ topic: process.argv[2] })
await raft.ready()
raft.becomeLeader(1)
raft.appendLog({ op: 'set', k: 1 })
console.log(raft.commitIndex(), raft.getStats())

Docs

docs/api.md · docs/architecture.md

Test

npm install && npm test · bare examples/basic.js [topic]