state-machine-replication · also State machine replication, Replicated state machine

State-machine replication

State-machine replication maintains a service across replicas that start from a common state and apply deterministic transitions to the same ordered inputs.

Related Observatory article: Read on hesela.com

Agreement on inputs does not make arbitrary code deterministic. Local clock readings, random choices and external input must be coordinated or supplied as agreed input. Matching state is expected at the same applied prefix, not at every instant. [1]

A committed log entry can await local application. A log-free linearizable read needs current authority and sufficient application progress; a replicated log alone also does not suppress repeated client commands. [2]

The abbreviation SMR also denotes shingled magnetic recording; this record uses the full name to avoid confusing replication with disk recording.

Relations

related
Consensus, Raft, Paxos

Citations

  1. Schneider. Implementing Fault-Tolerant Services Using the State Machine Approach: A Tutorial (1990), sections 1, 3 and 7.2; DOI 10.1145/98163.98167. (accessed 2026-11-16)
  2. Ongaro and Ousterhout. In Search of an Understandable Consensus Algorithm, extended version (20 May 2014), sections 2 and 8. (accessed 2026-11-16)
Sources & caveats
  • Synthesis of the deterministic state-machine approach and Raft's client protocol. No cluster benchmark, recovery test or universal fault threshold is claimed.

JSON: /data/terms/state-machine-replication.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. State-machine replication. Hesela. 2026-11-16. https://hesela.dev/terms/state-machine-replication/