GraphQL vs REST vs gRPC vs tRPC — Choosing Your API Protocol

You're designing a new API. Or you've inherited a project and you're wondering why they chose GraphQL over REST (or vice versa). Or you're arguing with someone on the internet about which protocol is "best."

Here's the uncomfortable truth: there is no universally best API protocol. Each was designed to solve specific problems, and the right choice depends on your context — who's calling the API, what data patterns you have, how your team works, and what ecosystem you're already invested in.

Let's build a decision framework instead of picking sides.

The Contenders

REST — The Reliable Standard

REST (Representational State Transfer) is the default choice for web APIs. It uses standard HTTP methods and URLs to represent resources:

GET    /api/users/42         → Fetch user