Read replica
A read replica is a database copy that receives replicated data from a primary and serves read operations, typically separately from writes.
Fast by Default
A read replica is a database copy maintained primarily to serve read operations, often to distribute read load or support another region.
- How it is used
- Scales read-heavy database workloads by moving read traffic from a primary to replicated servers.
- How deep it goes
- Explains primary-write and replica-read roles, replication lag, synchronous versus asynchronous trade-offs, and lag-sensitive routing constraints.
- Examples
- Uses a stale profile view after an update, Figma’s capacity response, and a multi-region PostgreSQL deployment with nearly 50 replicas.
- What you can do after
- Evaluate/understand when read traffic can move to replicas and when replication lag makes a read path unsafe.
Clean Applications with Hexagonal Architecture
A copy of data maintained from a source system and used to serve reads.
- How it is used
- Supplies locally readable data owned by another context when queries can tolerate replication lag.
- How deep it goes
- Explains selection, boundary mapping, update failure modes, and operational duties without detailing a replication implementation.
- Examples
- Uses an article query that reads an author’s display name from data owned by an author service.
- What you can do after
- Evaluate read strategies per query against freshness, response time, coupling, and the cost of maintaining a local copy.
Read how Clean Applications with Hexagonal Architecture explains read replica →
PostgreSQL Mistakes and How to Avoid Them
A read replica is a database server that receives replicated data and serves read operations rather than accepting the authoritative writes.
- How it is used
- Deploys read replicas for read traffic while directing authoritative writes to the primary.
- How deep it goes
- Explains replication lag, stale reads, recovery conflicts, and distributed transaction consequences without detailing replication internals.
- Examples
- Demonstrates account-balance reads and writes across a delayed standby and primary, plus a query canceled by recovery.
- What you can do after
- Diagnose stale-read failures and recognize when application logic requires coordinated transactions across database nodes.
Read how PostgreSQL Mistakes and How to Avoid Them explains read replica →
Also covered in
- Microsoft Azure in Action
- Grokking Software ArchitectureIn early access (MEAP)
- Simple Object-Oriented Design: Create clean, maintainable applications
What to know first
- cachingCaching is the temporary storage of data or computed results for reuse, reducing the work or delay of retrieving or computing them again.
- connection poolingConnection pooling is a resource-management technique that maintains a managed collection of established connections for reuse across operations.
Related concepts
- projectionalternative to · A projection is a derived, query-oriented representation of selected data, often maintained from events or a domain model.
- denormalizationalternative to · Denormalization is the deliberate combination or duplication of related data in a data model, often to simplify access or improve retrieval performance.
- replication laguses · Replication lag is the delay between a change being applied to a source and becoming available or applied at a replication target.
- dataset splitalternative to · A dataset split is the division of a dataset into distinct subsets assigned different purposes, such as training, validation, or evaluation.
Questions about read replica
What is read replica?
A read replica is a database copy that receives replicated data from a primary and serves read operations, typically separately from writes.
Which Manning books explain read replica?
Fast by Default, Clean Applications with Hexagonal Architecture and PostgreSQL Mistakes and How to Avoid Them.
What should I know before learning read replica?
Manning books that teach read replica usually introduce caching and connection pooling first.
What is the difference between read replica and projection?
A read replica is a database copy that receives replicated data from a primary and serves read operations, typically separately from writes. A projection is a derived, query-oriented representation of selected data, often maintained from events or a domain model.
What kinds of read replica are there?
Kinds of read replica include hot standby.
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.


