Difference between GraphQL and REST

The main difference between GraphQL and REST is that GraphQL is focused on being a utility for data access, while REST is a design principle for scalable web services.

REST API principles originate from the late 1990s, while GraphQL was introduced in 2012 to address the limitations of REST.

Illustration showing differences between REST and GraphQL API. REST API takes 3 requests compared to GraphQL that only takes one.

GraphQL is more efficient than REST because it gets the exact information the client needs while REST includes the entire resource.

Differences between GraphQL and REST

Feature GraphQL REST
Purpose Query language Design principle
Data fetching Pulls data from a database Works with domain-level resources
API structure Client can request exactly what it needs

Fixed structure with defined endpoints for each resource

# of requests Single request Multiple round trips
Popularity 24% 1 91% 1
Introduced in 2012 2000
Bandwidth usage Low High
Caching Difficult Easy



Media type Limited to JSON Can use all HTTP media types
Client-server coupling More coupled Less coupled
Data control Gives more control over returned data Over-fetching or under-fetching issues
Error handling Communicated through the response structure Uses HTTP Status codes
1 usage according to a 2021 survey from Smartbear

What is a REST API?

REST is an architecture style for designing APIs.

Roy Fielding defined RESTful API design in 2000 in his Ph.D. dissertation at the University of California, Irvine.

The key components that define RESTf are:

  • Identification of resources: Unique URIs.
  • Manipulation of resources through representations: Resources can be represented in different formats as defined by Media Types (e.g. JSON, XML, image)
  • Self-descriptive messages: Client-server communication uses features of the HTTP protocol to provide metadata (e.g. HTTP Methods, Headers, Content Negotiation)
  • Hypermedia as the engine of application state: The client navigates through the API using links included in the resource representations.

What is GraphQL?

GraphQL is an open-source query language for retrieving data through APIs.

It was designed to present data in a more concise and usable format, using objects and properties, instead of relying on individual REST API calls.

Facebook engineers Lee Byron, Dan Schafer and Nick Schrock created GraphQL in 2012 to address the limitations of REST API in delivering data to their mobile app.

In 2015, it was open-sourced and quickly adopted by other companies such as Airbnb and GitHub.

GraphQL demo

How does GraphQL work?

From the client's perspective, GraphQL works as follows:

  1. Building a schema: Schema is a description of all the possible queries and types that a GraphQL API returns. The schema requires strong typing using the Schema Definition Language (SDL).
  2. Validating queries: Before making a query, clients can validate their queries against the schema to ensure that the server can respond to it.
  3. Sending a single query: The client sends a single query to the server.
  4. Interpreting operations: The server interprets the query against the entire schema.
  5. Resolving data: GraphQL operation gathers the requested data from various data sources.
  6. JSON response: The API returns a JSON response with exactly the shape of the data requested.
Steps explaining how GraphQL works

How does REST work?

From the client's perspective, REST works as follows:

  1. Identify the resource that needs to be accessed or manipulated
  2. Choose an appropriate HTTP method (e.g. GET, POST, PUT, DELETE) based on the desired action to be performed on the resource
  3. Construct the request URL based on the resource identifier and any query parameters needed
  4. Send the request to the server
  5. Parse the response received from the server which is in the form of an HTTP response with a status code, headers and the response body (usually in JSON or XML format)

Disadvantages of REST that inspired GraphQL

The main disadvantage of REST design is a standardized form of representing resources.

Even Roy Fielding recognized it in his dissertation:

The trade-off, though, is that a uniform interface degrades efficiency, since information is transferred in a standardized form rather than one which is specific to an application’s needs. - Roy Thomas Fielding

This standardized form leads to over-fetching or under-fetching of data.

Example showing differences between GraphQL and REST API in fetching data.
The example shows how to get `capital` and `currency` values from GraphQL compared to REST API. In GraphQL, we can get exactly what we want, while the REST API results in over-fetching.

Differences between GraphQL and REST

Can you even compare REST and GraphQL?

GraphQL is focused on being a utility for data access, while REST is a design principle for scalable web services.

Roy T. Fielding's take on GraphQL:

Tweet from Roy T. Fielding: From an architectural styles perspective, #GraphQL is remote data access (RDA). It has all of the benefits and failings of early SQL, without the database vendors driving it sideways (yet). JSON readability adds little to that; lenient schema enforcement is a real improvement.

Detailed comparison of GraphQL and REST:


REST has high bandwidth usage because of the chatty interface. That's exactly why Facebook engineers created GraphQL. They need to reduce bandwidth usage for the mobile app.

GraphQL can reduce the size of the returned JSON documents by 94% in terms of the number of fields and 99% in terms of bytes, according to the study of 24 queries performed by seven open-source clients of two popular REST APIs (GitHub and arXiv) and 14 queries performed by seven empirical papers.

The study also shows that it is not straightforward to refactor API clients to use complex GraphQL queries due to the tendency of developers to organize their code around small functions that consume small amounts of data.


The implementation of caching in GraphQL requires more effort and complexity compared to REST.

Caching in REST is relatively simple as it uses a uniform resource representation. This means that the resources requested can easily be cached and reused without requiring any additional processing.

On the other hand, caching in GraphQL is more complex due to the nature of the queries and representations. GraphQL queries are more complex and can include multiple fields, making it difficult to cache the results of these queries.


REST API versioning is a complex topic. Some argue that REST API shouldn't be versioned. But that's far from reality. Most REST APIs use some kind of versioning -- URL, query params, headers, etc.

Versioning is more important for REST than GraphQL APIs because in REST we request the resource and not the individual fields.

GraphQL only returns the data that you explicitly request, so new capabilities can be added through new types and fields. This allows for a common practice of avoiding breaking changes and serving a versionless API.

REST API URI Versioning Example
REST API Versioning Example

Data Types

GraphQL is limited to JSON as the media type, while REST can use all HTTP media types.

Do you need more than JSON?

Many systems do. Let's say you wanted to transfer an image file.

With REST, you can just respond with the image/jpeg media type.

On the other hand, GraphQL is more complicated. You can send an image by encoding it as a base64 string and including it as a string in your GraphQL query. Then the client needs to interpret the encoded string to figure out it's an image.

Client-server coupling

GraphQL has more coupling between the client and the server because the client needs to understand the schema to make a query.

One of the key principles of REST is Hypermedia as the Engine of Application State (HATEOAS).

HATEOAS is a principle of REST service that adds hypermedia links to REST responses to help discover all available resources.

The advantage of HATEOAS is that you don’t need to know all URIs up front. The API provides them with the rest of data so you can discover actions and resources by inspecting the API’s responses.

HATEOAS link example
Example of HATEOAS in REST API


With GraphQL, there is a single point of interaction between the client and the server, whereas, with REST, there are multiple endpoints for different operations.

This difference in design can impact the complexity of the API and the way it's used by client applications.

For smaller APIs, GraphQL may seem more complex due to its need for a schema, while REST uses endpoints. But, as the number of endpoints increases, GraphQL's simplicity shines as it allows for querying all data from a single endpoint, reducing the need for multiple requests and endpoints.

Difference in complexity GraphQL schema vs REST API (OpenAPI)


We can make general conclusions on performance differences because performance depends on the individual system.

But keep this in mind...

GraphQL can be prone to performance issues because it allows for more complex queries, which can be time-consuming and increase the load on the server.

On the other hand, REST has a fixed structure and limits the amount of data that can be requested in a single call, which can help to mitigate performance problems.

Error Handling

REST API error handling is usually done by returning specific HTTP status codes (such as 400 for Bad Request or 500 for Internal Server Error) along with error details in the response body. This makes it easy to map errors to specific categories and monitor them using tools that rely on HTTP status codes.

REST API error handling example
Problem Detail response example from Backend.AI

With GraphQL, all responses have a 200 HTTP status code regardless of success or failure.

To indicate errors, the response body includes a "errors" field, which holds an array of error objects. This can make it harder for existing monitoring tools that rely on HTTP status codes to correctly categorize and monitor errors.


According to the 2021 survey from Smartbear, 91% of APIs use REST design, compared to 24% that use GraphQL (some systems use both).

REST still dominates with 91% saying they deliver APIs using that style. Perhaps surprisingly, SOAP is still holding strong at number two (57%), which sees an increase from 54% in 2019. Both GraphQL and gRPC have doubled in usage compared to 2019, from 12% to 24% and 4% to 8%, respectively.

Who uses GraphQL?

Several large companies have adopted GraphQL including Airbnb, GitHub, Netflix, and Twitter.

List of companies using GraphQL

Should I pick REST or GraphQL?

GraphQL is a better fit for complex systems that:

  • have nested relational (graph) data,
  • pull data from multiple APIs,
  • need efficient data loading (e.g. 3G Mobile Apps, PWAs)

The study shows a drastic reduction in the number of fields and size of returned JSON documents when using GraphQL instead of REST-based APIs.

REST vs GraphQL: Differences Summary

  • GraphQL is a query language, while REST is a design principle.

  • GraphQL is more about pulling data from a database, while REST works with domain-level resources that could be different from the underlying data structure.

  • REST APIs typically have a fixed structure, with a defined set of endpoints for each resource, while in GraphQL, the client can request exactly what it needs, making it more flexible.

  • REST APIs may require multiple round trips to fetch all the required data, while GraphQL allows to fetch all the required data in a single request, reducing the number of round trips and improving performance.

  • REST can have over or under-fetching issues, while GraphQL avoids that.

  • GraphQL is more prone to performance issues because it allows for more complex queries, which can be time-consuming and increase the load on the server. On the other hand, REST has a fixed structure and limits the amount of data that can be requested in a single call, which can help to mitigate performance problems.

  • GraphQL has more coupling between client and the server because the client needs to understand the schema to make a query.

  • GraphQL generates developer documentation using a standard schema definition, while REST APIs have various non-standard options such as OpenAPI, RAML, Postman, Blueprint, etc.

Josip Miskovic
About Josip

Josip Miskovic is a software developer at Americaneagle.com. Josip has 10+ years in experience in developing web applications, mobile apps, and games.

Read more posts →
Published on: