🔁Replication

NEW

Process of copying and synchronizing data across systems to improve availability, resilience, and read scalability.

DESCRIPTION

Replication duplicates data between nodes or regions to tolerate failures and serve distributed workloads. Strategies include synchronous replication for strong consistency and asynchronous replication for lower latency. Topologies range from primary–standby to multi-primary with conflict resolution. Replication supports disaster recovery, read scaling, and maintenance operations with minimal downtime. Correct configuration requires attention to durability, lag, conflict handling, and network reliability.

ALTERNATIVE DEFINITIONS

Wikipedia

Replication in computing involves sharing information so as to ensure consistency between redundant resources, such as software or hardware components, to improve reliability, fault-tolerance, or accessibility.

Broad computing perspective emphasizing redundancy and reliability.

Source

Microsoft

Replication is a set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between databases to maintain consistency.

Highlights database objects and bidirectional synchronization in SQL Server.

Source

IBM

Data replication is the process of storing data in more than one site or node to enhance data availability and accessibility.

Focuses on multi-site storage for availability and accessibility.

Source

RELATED TERMS

High Availability Failover Cluster Analysis Consistency Model Change Data Capture Multi-master Replication Log Shipping Eventual Consistency Sharding

COMPETING TERMS

Backup and Restore Erasure Coding

RELATIONS

• Narrower: Data Replication Multi-Region Replication State Machine Replication

KNOWLEDGE AREAS

Data Storage & Operations Data Engineering Infrastructure Data Architecture

TARGET AUDIENCE

Data Engineer DevOps Engineer Cloud Architect Data Architect

EXTERNAL SOURCES

• Wikipedia - Replication (computing)
• PostgreSQL - Streaming replication guide
• Microsoft - SQL Server replication
• MongoDB - Replica sets overview
• AWS - RDS Multi-AZ replication

TOP QUESTIONS

Why is Replication used instead of just backups?

Replication provides near real-time copies for availability and read scaling. Backups focus on recovery points, not live failover or latency reduction.

Category: Misunderstanding

What are the main Replication strategies?

Synchronous for strong consistency, asynchronous for lower latency, and semi-synchronous for a compromise. Topologies include primary–standby and multi-primary.

Category: Example

What risks come with asynchronous Replication?

Lag can cause stale reads and potential data loss during failover. Monitoring and bounded lag strategies mitigate these risks.

Category: Risks

How is conflict handled in multi-primary Replication?

Strategies include last-writer-wins, causal ordering, CRDTs, or application-level resolution. Clear policies are essential to maintain correctness.

Category: Management

When should I choose synchronous Replication?

Use it when zero data loss and strong consistency are critical, and latency budgets can accommodate commit delays across replicas.

Category: Opinion

How does Replication support disaster recovery?

Geo-replicas provide failover targets in other regions. Regular switchover tests validate RPO/RTO and runbooks.

Category: Best practice

What is a common mistake with Replication monitoring?

Only tracking link health without measuring replication lag and apply latency. Comprehensive metrics and alerting are essential.

Category: Mistakes

How does Replication impact performance?

Synchronous replication increases write latency; asynchronous reduces it but risks lag. Offloading reads improves overall throughput.

Category: Requirements

Is Replication a substitute for backups?

No. Replication propagates corruption and deletes. Backups provide point-in-time recovery and protection against logical errors.

Category: Risks