leader–follower replication
Send writes through a leader and replicate them to followers.
Use this when You need read capacity or a standby while keeping one write authority.
without the term
“We need another database copy for reads and recovery, with one place accepting writes. Explain the setup.”
with the term · How do you ask a model for leader–follower replication?
Document leader–follower replication, including acknowledgement policy, stale reads, and safe promotion checks.
What is leader–follower replication?
A leader accepts writes and followers apply its changes. Acknowledgement policy determines whether a successful write has reached or been applied by followers; asynchronous followers may lag.
Why does leader–follower replication matter when vibe coding?
An agent can route a read-after-write to a lagging follower or promote a stale copy.
How do you do leader–follower replication?
Define write and read routes, acknowledgement guarantees, and promotion rules. Check replica lag and read-after-write behavior during a failover drill.
What goes wrong with leader–follower replication?
One leader simplifies write ownership but does not eliminate data loss, lag, or split-brain risk.
Sources for this entry
- PostgreSQL: Log-shipping standby servers
Primary/standby streaming replication, asynchronous lag, and synchronous acknowledgement configurations.
- PostgreSQL: Failover
Promotion, client routing, preventing the old primary from continuing as a writer, and restoring redundancy.
Sources checked . Source checks do not establish human editorial approval. How we check content.