How igotlinux/raft-kv works
This is a five-node Raft-replicated key-value service. A client sends a write to a node’s HTTP API; the API proposes it through the store to Raft, which replicates and commits log entries. The store applies committed entries and the API returns the outcome; reads use local state, while non-leader writes receive a leader hint. Raft persists log and term state, and nodes communicate over HTTP. The admin API configures live fault injection. The graph follows the README and shown wiring; unsampled internals are not inferred.
Main entry points: main.go Node Bootstrap · raft.go Raft Node · http_api.go KV HTTP API · store.go KV Store
Components 12
Client API
- KV HTTP API
internal/kv/http_api.go
Replicated State
- KV Store
internal/kv/store.go - WAL Persister
internal/raft/persister.go
Raft Consensus
- Raft Node
internal/raft/raft.go - Log and Commands
internal/raft/types.go - Raft RPC Types
internal/raft/rpc.go - HTTP Transport
internal/transport/http.go
Node Operations
- Fault Admin API
internal/transport/admin.go - Fault Injector
internal/transport/http.go - Node Bootstrap
cmd/server/main.go
Other components
- Client
- Peer Raft Node
Connections 18
- Client → KV HTTP API: sends requests
README.md - KV HTTP API → KV Store: proposes writes
internal/kv/http_api.go - KV HTTP API → KV Store: reads local state
internal/kv/http_api.go - KV HTTP API → Raft Node: reads status
internal/kv/http_api.go - KV Store → Raft Node: starts commands
internal/kv/store.go - Raft Node → KV Store: delivers commits
README.md - Raft Node → WAL Persister: persists log state
internal/raft/raft.go - Raft Node → HTTP Transport: sends peer RPCs
README.md - HTTP Transport → Peer Raft Node: sends HTTP RPCs
internal/transport/http.go - Peer Raft Node → HTTP Transport: calls RPC handlers
internal/transport/http.go - Fault Admin API → Fault Injector: sets fault modes
internal/transport/admin.go - Fault Injector → HTTP Transport: filters outbound RPCs
internal/transport/http.go - Node Bootstrap → WAL Persister: creates
cmd/server/main.go - Node Bootstrap → HTTP Transport: configures
cmd/server/main.go - Node Bootstrap → Raft Node: starts node
cmd/server/main.go - Node Bootstrap → KV Store: runs state machine
cmd/server/main.go - Node Bootstrap → KV HTTP API: registers API
cmd/server/main.go - Node Bootstrap → Fault Admin API: registers admin routes
cmd/server/main.go