read replica
A read replica serves a copy of database data.
Use this when Read-heavy work competes with writes on the primary database.
without the term
“Reports are slowing down the main database. Can we send read queries to a copy? But I'm worried users won't see what they just saved.”
with the term · How do you ask a model for read replica?
Route only suitable reads to this replica. Test lag after a write and preserve the consistency required by user-facing confirmations.
What is read replica?
A read replica serves queries from replicated data rather than handling the primary write workload. Asynchronous replicas can lag behind, sometimes substantially; acknowledgement and read guarantees depend on the selected replication mode.
Why does read replica matter when vibe coding?
A recent write can appear missing when its next read reaches a lagging replica.
How do you do read replica?
Classify reads by consistency requirements and observe replication lag.
What goes wrong with read replica?
Sending a read-after-write to a lagging replica and treating missing data as a failed write. Replicas do not replace backups.
Sources for this entry
- PostgreSQL: Log-shipping standby servers
Primary/standby streaming replication, asynchronous lag, and synchronous acknowledgement configurations.
Sources checked . Source checks do not establish human editorial approval. How we check content.