Ac Distributed State And Replication

Keeping copies of data consistent when there is more than one copy: replication topologies and what each promises, read replicas and their staleness, leader election and split-brain prevention, quorum reads and writes and the arithmetic of their overlap, vector clocks and conflict detection, CRDTs and conflict-free merges, read-your-writes and session guarantees, and the written replication record. It explains the guarantees a replicated store can and cannot give; it never recommends a database product and never promises a consistency level. Use when asking "read replica", "replication lag", "split brain", "leader election", "quorum", "vector clock", "CRDT", "read your writes", "eventual consistency", "write conflict", "why did my write disappear", "stale read". Not for cache correctness and TTL choices (ac-caching-and-invalidation), not for schema migrations and backfills (ac-database-changes), not for event delivery between services (ac-event-driven-architecture).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit b711a7ac41

Frequently asked questions

npx get-skill add jiayaoqijia/ac-distributed-state-and-replication