Replication

Turkish equivalent: ReplikasyonDomain: Distributed Systems

The maintenance of multiple copies of data or state across nodes to improve availability, locality, durability, or read scalability.

Distributed-Systems Context

Replication keeps multiple copies of data or state to improve availability, locality, durability, or read capacity. Leader-follower, multi-leader, and leaderless designs make different trade-offs in consistency, conflict resolution, write availability, and operational complexity.

Durability Boundary

Replication is not a backup. A user mistake, bad deployment, or logical corruption can be propagated to every replica, while replication lag can create stale reads and a window of data loss during failover.

Related technical publications

Publications whose title or summary directly references this concept.

Concurrency in Distributed Data Systems

Concurrency in distributed data systems depends on the interaction of MVCC, isolation levels, lost updates, write skew, and replication visibility rather than on a single database setting.