synchronous replication

Replication in which a write is only acknowledged after another copy has durably stored it.

In more detail

It protects committed writes against losing one machine, at the cost of extra latency and a new dependency: if the other copy is slow, every write is slow. Databases often let you choose it per transaction or per replica.

Examples

ship(primary, near)   # synchronous: before we say "paid"
Primary fails at 14:37: the synchronous replica still holds all 169 orders.

Related terms

Taught in

References