GraphQL
GraphQL is a query language for APIs that lets clients request exactly the data they need in a single request, rather than making multiple calls to different REST endpoints.
GraphQL was developed by Facebook (Meta) and released publicly in 2015 as an alternative to REST APIs. While REST uses multiple endpoints with fixed data structures, GraphQL uses a single endpoint where the client specifies exactly what data it wants using a query language. The core advantage is flexibility.
With GraphQL, you send a single query that returns exactly those fields and nothing more. GraphQL uses a typed schema to define all available data and operations. This schema serves as a contract between frontend and backend teams, automatically generates documentation, and enables powerful development tools with autocomplete and validation.
In practice
- A social media app switched from REST to GraphQL and reduced their average API payload size by 60%, improving mobile app load times on slow networks
- A content platform used GraphQL to serve different data structures to their web app (full articles), mobile app (summaries), and smartwatch app (headlines only) from a single API
- GitHub's public API v4 uses GraphQL, allowing developers to fetch complex nested data (repos, issues, PRs, comments) in a single request instead of dozens of REST calls
- An e-commerce company implemented GraphQL and enabled their frontend team to build new features 30% faster because they could query any data combination without backend changes
More in Web development
- Responsive Design
- Progressive Web App (PWA)
- Single-Page Application (SPA)
- Server-Side Rendering (SSR)
- Static Site Generation (SSG)
- API (Application Programming Interface)
- CMS (Content Management System)
- Headless CMS
- Version Control
- CI/CD (Continuous Integration / Continuous Deployment)
- JavaScript Framework
- TypeScript
Not sure how this applies to you?
A senior engineer walks your site, your search presence and the way enquiries reach you, then writes down the three things worth fixing first. You keep the document either way.