Replication

Configuring leader-follower or streaming replication at the database-engine level — the infra side of what ConsistencyConcurrency/Replication covers conceptually.

Why we need this / what value this brings

Protects against data loss on primary failure and offloads read traffic, without the complexity of sharding.

When to use this

Once read load is affecting write performance, or an SLA requires a hot standby for failover.

How to use or implement this

Set up one streaming read replica for reporting/analytics queries first — that alone often resolves the read-load pressure this is meant to solve.

Research questions

• Does Localz's current Postgres setup (docker-compose) have any replication configured, or is it single-instance?

---

Empty folder — drop notes, links, and findings here as you research.