Synchronous replication
Synchronous replication is a replication method in which an operation is acknowledged or completed only after required replicas have confirmed the change.
100 SQL Server Mistakes and How to Avoid Them
Synchronous replication propagates each data change to a secondary system and waits for its completion before completing the change on the primary.
- How it is used
- Uses synchronous replication to provide high availability while preventing data loss after unexpected failure.
- How deep it goes
- Explains write acknowledgment and latency consequences, but stops short of configuration or diagnostic procedures.
- Examples
- Uses local availability groups and geographically separated data centers to contrast automatic failover with latency-sensitive replication.
- What you can do after
- Evaluate whether synchronous replication fits a topology by weighing data-loss protection against network latency and write performance.
Read how 100 SQL Server Mistakes and How to Avoid Them explains synchronous replication →
PostgreSQL Mistakes and How to Avoid Them
Synchronous replication requires configured replication standbys to confirm replicated changes before the committing transaction completes.
- How it is used
- Uses synchronous replication when extreme correctness outweighs performance and stale reads are unacceptable.
- How deep it goes
- Explains commit confirmation, conflict prevention, network latency, and distributed-transaction limits without configuration details.
- Examples
- Demonstrates a long-running standby report conflicting with primary updates and VACUUM cleanup.
- What you can do after
- Evaluate whether synchronous confirmation justifies its latency when choosing consistency guarantees for replicated workloads.
Read how PostgreSQL Mistakes and How to Avoid Them explains synchronous replication →
Related concepts
- replicationcontrasts with · Replication is the creation or maintenance of multiple copies of data, state, or functionality across separate locations or components.
- replication lagcontrasts with · Replication lag is the elapsed delay between a change being applied or committed at a source and becoming applied or visible at a replication target.
- acknowledgmentuses · An acknowledgment is a protocol message or signal confirming that transmitted data, a message, request, or operation was received or processed.
- failoverproduces · Failover is the transfer of service or workload from a failed or unavailable component to a functioning alternate or standby component.
- uptimeimplements · Uptime is the duration or proportion of a specified period during which a system or service is operational and available to provide its intended function.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.