Database / Supabase Intermediate to Advanced Interview Questions
When should you use a read replica versus scaling the primary database's resources?
Scaling the primary (more CPU, RAM, or storage) helps when both reads and writes are the bottleneck, or when the workload doesn't tolerate any replication lag — for example, a checkout flow that must read back data it just wrote. It's also the simpler change, since it doesn't introduce a second connection target for your application to reason about.
A read replica makes more sense when reads vastly outnumber writes and the write path itself isn't the constraint — a content site serving thousands of read-only page views per write, or an internal analytics dashboard hammering the same tables users are actively writing to. Routing that read traffic to a replica keeps it from competing with production writes for the primary's resources, at the cost of accepting eventual consistency for anything read from the replica.
More Related questions...