Reads on replicas, writes on the primary
The setup
The @prisma/extension-read-replicas extension routes read queries to replicas automatically, while transactions and writes stay on the primary.
- Create one client per URL.
- Extend the primary client with the replicas.
- reads go round-robin
$primary()forces the primary
- Verify TLS against your own CA.
Watch out for
- Replication lag right after a write
pg_hba.confrules are not replicated- The total number of connections
Replicas help with reads, not with writes.
For a read-heavy, write-light blog, the win is immediate.
Published: