MainExamplesHistoryRecommended Reading
GraphQL is a query language and runtime for APIs. Instead of making multiple requests to different endpoints, you make one request asking for exactly the data you need. It's like ordering at a restaurant: instead of getting a fixed meal, you specify exactly what you want.
How It Works:
- Single endpoint: One URL for all queries
- Query language: Describe the data you want
- Get exactly what you need: No over-fetching or under-fetching
- Strongly typed: Schema defines what's possible
GraphQL Query Example:
query {
user(id: 123) {
name
email
posts {
title
}
}
}
Benefits:
- Efficient: Get only the data you need
- Flexible: Client controls the response shape
- Single request: Fetch related data in one query
- Type-safe: Schema prevents errors
- Introspection: Can query the schema itself
When to Use:
- Complex data needs: Different clients need different data
- Mobile apps: Reduce data transfer
- Rapid iteration: Frontend can request new fields without backend changes
FAQ
Is GraphQL better than REST?
Not necessarily. REST is simpler and more established. GraphQL is better when you need flexible queries and want to reduce over-fetching.
Do I need GraphQL?
For simple APIs, REST might be enough. GraphQL shines when you have complex data relationships and multiple clients with different needs.