- 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]>
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]