# GraphQL vs. REST

DevFeed: [GraphQL vs. REST](<https://devfeed.tech/articles/graphql-vs-rest-23352.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/graphql-vs-rest>)

Author: Sashko Stubailo

Published: 2017-06-27T18:36:00Z

Content type: comparison

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [API](<https://devfeed.tech/topics/api.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [JSON](<https://devfeed.tech/topics/json.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Front end](<https://devfeed.tech/topics/frontend.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [article](<https://devfeed.tech/tags/article.md>), [backend](<https://devfeed.tech/tags/backend.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [http](<https://devfeed.tech/tags/http.md>), [json](<https://devfeed.tech/tags/json.md>), [rest](<https://devfeed.tech/tags/rest.md>)

## AI overview

This article compares GraphQL and REST at a technical level. It explains that both use HTTP requests and can return JSON, while GraphQL separates data descriptions from retrieval methods and lets clients request the data they need.

## Source excerpt

Edited by Ceora Ford Often, GraphQL is presented as a revolutionary new way to think about APIs. Instead of working with rigid server-defined endpoints, you can send queries to get exactly the data you're looking for in one request. And it's true -- GraphQL can be transformative when adopted in an organization, enabling frontend and backend teams to collaborate more smoothly than ever before.