GraphQL vs REST vs gRPC

Also Known As

TL;DR

Explanation

REST: resource-based (nouns in URLs), standard HTTP methods, cacheable with CDN, well understood — best for public APIs and simple CRUD. GraphQL: client specifies exact fields needed, single endpoint, eliminates over/under-fetching, but complex caching and N+1 risks — best for frontend-driven APIs with diverse client needs. gRPC: Protocol Buffers binary serialisation, HTTP/2, bidirectional streaming, strongly typed contracts, 5-10x faster than JSON REST — best for internal microservice communication where performance matters.

Common Misconception

Why It Matters

Common Mistakes

• GraphQL for internal service communication — gRPC is faster and better typed.
• REST for APIs with deeply variable client data needs — GraphQL handles this naturally.
• No DataLoader with GraphQL — N+1 problem makes GraphQL slower than REST without it.
• gRPC for browser-facing APIs — gRPC requires grpc-web proxy for browser clients.

Code Examples

// REST for mobile app — persistent over-fetching:
GET /api/users/42
// Returns: all 25 fields
// Mobile needs: name, avatar (2 fields)
// 23 fields wasted on every request

// Right tool for the job:

// Public REST API — simple, cacheable, well-understood:
GET /api/products/42          → product data (CDN cacheable)

// GraphQL for mobile/web with varied needs:
query { user(id:42) { name avatar } }  → exactly 2 fields

// gRPC for internal PHP microservices:
// payment.proto: rpc Charge(ChargeRequest) returns (ChargeResponse)
// Generated PHP client + binary protocol
// 5x faster than JSON REST for high-frequency calls

References

• ↗ https://www.apollographql.com/docs/

Tags

Related Terms