asynchronous replication
Replication in which a write is acknowledged first and copied to other machines afterwards.
In more detail
It is faster and allows distant copies, but a crash of the leader can lose writes that were acknowledged and not yet copied. It is also the source of replication lag.
Examples
if t.minute % 15 == 0: ship(primary, far) # asynchronous: every fifteen minutesPrimary fails at 14:37: the asynchronous replica stops at 14:30, three orders short.Related terms
- synchronous replication — Replication in which a write is only acknowledged after another copy has durably stored it.
- RPO — Recovery point objective, the most data a business can afford to lose in an outage, measured as the time before the failure.
- geographic dispersion — Placing a primary site and its recovery site far enough apart that one local disaster cannot knock out both.
- replication — Keeping copies of data in more than one place, updated automatically, so one failure does not lose or block it.
- replication lag — How far behind the leader a replica is, measured in time or in writes.
Taught in
- Disaster Recovery Sites: Hot, Warm & Cold — Cybersecurity Fundamentals, GRC & Cryptography
- Replication, Failover And Leader Election — Scalable System Design & Distributed Architecture