Why MicroRaft?

What it is

MicroRaft is a library implementation of the Raft consensus algorithm.

• transport
• persistence layer
• serialization format
• threading model
• state machine logic

This makes it a strong fit for custom metadata stores, control planes, coordination services, and other CP subsystems.

Why choose it

• a lightweight embeddable dependency instead of an external cluster product
• a modular design that does not force your transport or storage stack
• production-oriented Raft capabilities such as snapshotting, membership changes, quorum-aware queries, pre-voting, and leadership transfer
• explicit control over operational behavior instead of a sealed appliance

What you are signing up for

• you will define your own transport and persistence boundaries
• you will still need to think about operational rollout and recovery
• you get control, but you also keep responsibility

When not to use it

• a turnkey distributed key-value store
• a managed lock service or service registry
• a platform that hides consensus internals from application engineers
• immediate multi-language client support out of the box

In those cases, a higher-level system may be a better fit than a library.