← Back to the chapter · Next detail →
Technical detail · CAP Theorem and Database Categories
Quorums, timeouts and one firmware target
Quorum shorthand can help explain the intuition. If reads and writes must overlap across replicas, a later read can observe an accepted write under the assumptions of that system. The shorthand does not prove safe behavior by itself. The assumptions around clocks, failover, stale replicas, client retries, region latency, and application-level conflict handling still need evidence.
Worked example: a three-replica store requires two acknowledgements before accepting a firmware desired-state write. If one replica is isolated, the write can still be accepted by the two connected replicas, but a client timeout can make the operator retry. The release test must show whether the retry carries the same operation id, whether the store treats it as the same write, and whether the isolated replica receives the accepted version after reconnect. Without those mechanics, a “quorum write” label does not prove that devices see one target.