The GraphQL vs REST debate is one of the most searched API topics. In 2026, both have evolved — REST with OpenAPI 3.1 and GraphQL with federation and persisted queries. Let's break down the real trade-offs.
📊 REST vs GraphQL at a Glance
| Feature | REST | GraphQL |
|---|---|---|
| Data Fetching | Multiple endpoints | Single endpoint, exact fields |
| Over-fetching | Common problem ⚠️ | Solved ✅ |
| Caching | HTTP cache built-in ✅ | Requires client-side cache |
| Learning Curve | Low ✅ | Medium ⚠️ |
| Real-time | WebSockets (separate) | Subscriptions built-in ✅ |
| File Upload | Native ✅ | Requires multipart spec |
🔵 REST API Example
// Express.js REST API
app.get('/api/users/:id', async (req, res) => {
const user = await db.users.findById(req.params.id);
res.json(user); // Returns ALL fields — over-fetching!
});
// Client needs 3 requests for a profile page:
// GET /api/users/123
// GET /api/users/123/posts
// GET /api/users/123/followers
🟣 GraphQL Example
// GraphQL — single request, exact data
const GET_USER_PROFILE = gql`
query GetUserProfile($id: ID!) {
user(id: $id) {
name
avatar
posts(limit: 5) {
title
createdAt
}
followersCount
}
}
`;
// One request, exact fields, no over-fetching!
🆕 The Third Option: tRPC
// tRPC — End-to-end type safety without schemas
import { initTRPC } from '@trpc/server';
const t = initTRPC.create();
export const appRouter = t.router({
getUser: t.procedure
.input(z.object({ id: z.string() }))
.query(async ({ input }) => {
return await db.users.findById(input.id);
}),
});
// Client — fully typed, no codegen needed!
const user = await trpc.getUser.query({ id: '123' });
// TypeScript knows the exact shape of 'user'
🎯 When to Use Which
- 📌 REST — Public APIs, simple CRUD apps, microservices, when HTTP caching matters
- 📌 GraphQL — Complex UIs with nested data, mobile apps (bandwidth matters), real-time features
- 📌 tRPC — Full-stack TypeScript apps where client and server share a codebase
💡 Bottom Line: Don't choose based on hype. REST is perfect for most apps. Use GraphQL when you have complex, nested data requirements. Use tRPC when you own both client and server in TypeScript.