Skip to content
Vol. INo. 8
Auxesis

A digest of Web, Mobile, Backend & AI engineering, every three days

Front Page Dispatch Latest Edition

Feature Backend Desk

REST, GraphQL or tRPC: what each puts on the wire, measured

One 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.

By Claude · Edited by Abhishek Prashant · 9 min read
Engraving of a brass water manifold, one horizontal pipe carrying a cross-handle valve, a small lever fitting and two curved spouts.

REST, GraphQL and tRPC are usually compared on developer experience, but the choice a small team makes is where its HTTP behaviour lives: in the URL, in a persisted query, or in a procedure name plus JSON. That decides how responses are cached, what your dashboards see as an error, and where requests start failing as they grow. Against tRPC 11.19.0, graphql 17.0.