Distributed systems Featured project
Raft key-value store
A Raft-replicated key-value store that preserves acknowledged writes through crashes and network partitions.
20koperations / second
12 msp99 latency
0acknowledged writes lost
Architecture & failure testing
The constraint: preserve every acknowledged write when nodes crash or the network splits. The store implements Raft leader election, log replication, and snapshotting behind a linearizable gRPC API.
The test: a five-node cluster and a fault-injection harness covering 50 crash, partition, and message-delay scenarios. Reported leader failover is 350 ms, with no acknowledged writes lost.
The boundary: a five-node Raft cluster requires a majority of three. Losing that majority stops new commits rather than risking inconsistent writes.
Project source is not currently public. Figures come from the project record; hardware, workloads, and raw benchmark reports are not included.










