Home/Learn/Replication
Topic

Replication

Learn Replication as a connected topic across chapters, concepts, simulations, and interview reasoning.

10 Concepts6 Articles1h 29m

Overview

Learn Replication as a connected topic across chapters, concepts, simulations, and interview reasoning.

How this topic helps

Distributed Systems
System Design
Consistency
Interview Prep

Learning Path in this Topic

Series that contain articles from Replication. Select a path to filter the article list.

Articles

6 matched articles

Article 1System Design Replication and Failover: Keep Services Alive When a Primary DiesTLDR: Replication means keeping multiple copies of your data so the system can survive machine, process, or availability-zone failures. Failover is the coordinated act of promoting a healthy replica, 15 minArticle 2Stale Reads and Cascading Failures in Distributed SystemsTLDR: Stale reads return superseded data from replicas that haven't yet applied the latest write. Cascading failures turn one overloaded node into a cluster-wide collapse through retry storms and redi25 minArticle 3Data Anomalies in Distributed Systems: Split Brain, Clock Skew, Stale Reads, and MoreTLDR: Distributed systems produce anomalies not because the code is buggy — but because physics makes perfect consistency impossible across network boundaries. Split brain, stale reads, clock skew, ca13 minArticle 4The Consistency Continuum: From Read-Your-Own-Writes to Leaderless ReplicationTLDR: In distributed systems, consistency is a spectrum of trade-offs between latency, availability, and correctness. By leveraging session-based patterns like Read-Your-Own-Writes and formal Quorum l8 minArticle 5A Guide to Raft, Paxos, and Consensus AlgorithmsTLDR TLDR: Consensus algorithms allow a cluster of computers to agree on a single value (e.g., "Who is the leader?"). Paxos is the academic standard — correct but notoriously hard to understand. Raft13 minArticle 6System Design Databases: SQL vs NoSQL and ScalingTLDR: SQL gives you ACID guarantees and powerful relational queries; NoSQL gives you horizontal scale and flexible schemas. The real decision is not "which is better" — it is "which trade-offs align w15 min