Section
Backend
BackendREST, GraphQL or tRPC: what each puts on the wire, measuredOne user lookup in three styles: tRPC’s batched GETs hit a 431 at 30 KB, GraphQL answers a failed query with 200, and only REST gives a cache a stable URL.BackendServerless Postgres connections: what each pooling layer protectsA frozen function instance keeps its idle Postgres connections, and a transaction pooler breaks named prepared statements unless it is told to track them.BackendFiltered vector search: where pgvector breaks and what to doOn 100,000 vectors, a 1% filter returned 0.33 of 10 requested rows from pgvector’s defaults. The Postgres planner, not the index, decides when that happens.
