# Read Replica

> A copy of a database that only answers reads. It takes load off the main one.

**Field:** Software Development  
**Category:** Databases  
**Also known as:** Replica, Read-Only Replica

## Think of it like

Think of it like extra menus on the tables. All can read one, but only the cook changes it.

## Definition

A read replica is a copy of a database that only answers reads. Writes still go to the primary, which sends each change on to the copy. Apps send big reports and searches to the copy, so the primary stays fast. The copy can be a bit behind, most often by under a second. That delay is called lag.

## Example

Jack's nightly sales report used to slow the shop down. Now it runs on a read replica, and shoppers never notice.

## Why it matters

Most apps read far more than they write. Replicas let reads grow without slowing the writes.

## Common mistake

Writing a row, then reading it back from a replica straight away. It may not have arrived yet.

## Three principles

- **Reads only.** Writes still go to the primary.
- **Spreads the load.** Reports run on the copy.
- **A little behind.** Replication lag is real.

## Related terms

- [Database Replication](https://learn.benibix.com/term/development/database-replication)
- [Database Sharding](https://learn.benibix.com/term/development/sharding)
- [Database Query](https://learn.benibix.com/term/development/query)
- [Database](https://learn.benibix.com/term/development/database)

---

Source: https://learn.benibix.com/term/development/read-replica
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
