Fix inaccuracies in replication explanation #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog
Synchronous replication means the leader waits for one or more replicas to acknowledge a write before confirming success to the client. This ensures strong consistency — if a write succeeds, it exists on all replicas — but increases write latency.
Asynchronous replication means the leader acknowledges a write immediately, then propagates it to replicas later. This provides better performance and availability, but replicas can temporarily lag (eventual consistency).
In databases, asynchronous replication usually happens continuously in near real-time; in backup or storage systems, it may happen on a schedule for cost reasons.