Offload read traffic to read replicas where appropriate

Offload read traffic to read replicas where appropriate | BeforeMerge Rules | BeforeMerge

Why this matters

Many workloads are read-dominated. Pointing every query at the primary wastes its write capacity and limits scalability. Replicas absorb read load, but watch for replication lag on reads that must be strongly consistent.

# Bad: every query hits the primary
const db = primary;
 
# Good: split reads and writes
const write = primary;
const read  = replica;  // tolerate small lag for read-only paths

Why This Matters

Related Rules

Catch this automatically on every PR

Why this matters