Definition
GraphQL is a query language for APIs that allows the requesting system to specify exactly which data fields it needs, rather than receiving a fixed response. Developed by Facebook and released publicly in 2015, it is an alternative to REST APIs. Instead of the server deciding what data to return, the client describes the shape of the data it wants, and the server responds with precisely that — nothing more, nothing less.
Why It Matters
GraphQL solves a specific problem: when a REST API returns too much data (wasting bandwidth) or too little (requiring multiple requests to assemble what you need). For businesses running mobile apps or complex dashboards that pull data from many sources, GraphQL can reduce load times and simplify development. However, it adds complexity on the server side and is not always the right choice. Understanding when GraphQL is recommended versus when REST is sufficient helps you evaluate whether a development team’s architecture decisions are genuinely driven by your needs.
Example
A mobile app showing a customer dashboard needs the customer’s name, their three most recent orders, and the status of their active support ticket. With a REST API, that might require three separate requests to three different endpoints. With GraphQL, the app sends a single request describing exactly those fields, and the server responds with all of it in one go — faster for the user and simpler for the developer to manage.