supabase-load-scale

# Supabase Load & Scale ## Overview Supabase scaling operates at six layers: **read replicas** (offload analytics and reporting queries), **connection pooling** (Supavisor pgBouncer replacement with transaction/session modes), **compute upgrades** (vCPU/RAM tiers), **CDN for Storage** (cache public bucket assets at the edge), **Edge Function regions** (deploy functions closer to users), and **table partitioning** (split billion-row tables for query performance). This skill covers each layer with real `createClient` configuration, SQL, and CLI commands. ## Prerequisites - Supabase project on a Pro plan or higher (read replicas require Pro+) - `@supabase/supabase-js` v2+ installed - `supabase` CLI installed and linked to your project - Database access via `psql` or Supabase SQL Editor - TypeScript project with generated database types ## Step 1 — Read Replicas and Connection Pooling Read replicas let you route read-heavy queries (dashboards, reports, search) to replica databases while keeping writes on the primary. Supabase uses **Supavisor** (their pgBouncer replacement) for connection pooling with two modes: **transaction** (default, shares connections between requests) and **session** (holds a connection per client session, needed for prepared statements). ### Configure the Read Replica Client ```typescript // lib/supabase.ts import { createClient } from '@supabase/supabase-js' import type { Database } from './database.types' // Primary client — handles all writes a...