Loading content
Data replication refers to strategies and techniques for distributing and synchronizing copies of data across nodes, sites, or systems. It addresses availability, latency, consistency and scalability in distributed architectures. Choosing synchronous, asynchronous or log‑based replication determines fault tolerance, performance and operational effort.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Data replication copies and synchronizes data across multiple nodes, sites, or systems to improve availability, fault tolerance, and read access.
In distributed databases and storage systems, data replication emerged from the problem of keeping the same data available despite failures, geographic distance, and load distribution. Approaches such as primary/standby, multi-primary, warm standby, streaming replication, and log-based transfer were developed to balance consistency, latency, and operational effort rather than maximize all goals at once.
Think of replication as a chain with three roles: a source produces changes, a transport path distributes them, and one or more replicas apply them. Depending on the method, write commands, transaction logs, or storage blocks are copied. Synchronous replication waits for the copy to catch up before acknowledging; asynchronous replication acknowledges first and reconciles later. That is why latency, failure window, and possible staleness differ.
A copy of the same data is kept on another node or storage location and updated continuously.
A delay can exist between a change at the source and its arrival on the copy.
Synchronous methods wait for acknowledgment; asynchronous methods reduce latency but accept a larger loss window.
Changes are derived from a change or transaction log and sent to target systems.
When the primary system fails, a replica takes over if it is current enough.
Replication matters for high availability, geo-redundant systems, read scaling, and recovery after outages. It is not a substitute for backups: errors can replicate too, and strong consistency often costs latency and operational effort. The key questions are RPO, RTO, network delay, conflict rules, and whether the main concern is reads, writes, or recovery.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.