Raft Task Queue
Distributed task queue built in Rust, with Raft consensus implemented from the original paper: leader election, log replication, an Axum REST API, and a real-time web dashboard.
The problem
A task queue that survives node failure can't just lock a database — it needs real distributed consensus so work is never lost or run twice when a node dies.
Under the hood
- API Server: Axum REST API on port 3000
- Raft Core: Leader election and log replication
- Task Queue: Task scheduling and executor
- Shared Types: Common types and messages
- Dashboard: Real-time web monitoring on port 8080
- Executor: Concurrent task execution with retries
Outcome
Written from the original Raft paper rather than a tutorial or an off-the-shelf crate: leader election and log replication across 5 Rust crates keep the cluster serving tasks through node failures with zero task loss. The queue itself benchmarks at 5M tasks/sec with 200 ns latency under Criterion.rs (100 iterations, 95% confidence intervals). That number is the in-memory single-node path — the queue's own cost, not a replicated-cluster throughput claim.
Want systems built like this?
I'm open to backend and platform work, contract or permanent — on-site in Belgium and the Netherlands, or fully remote for a team anywhere in the world, US and APAC hours included. EU citizen, so no sponsorship is needed. Tell me what you're building.