The document compares REST APIs and GraphQL, highlighting REST as a web standard for structured access to resources using HTTP verbs and resource-based endpoints, while GraphQL, created by Facebook, offers a flexible query language for efficient data fetching. GraphQL resolves issues of over- and under-fetching by allowing requests for precise data requirements. The summary notes the advantages of GraphQL in fetching and manipulating data compared to traditional RESTful methods.

1. GRAPHQL VS REST
JOHNNY HASHOUL
DECEMBER 2019

2. REST(FUL) API
WEB STANDARD FOR
DESIGNING APIS
STRUCTURED ACCESS TO
RESOURCES
HTTP VERBS (GET, POST,
PUT, DELETE)
RESOURCE BASED
ENDPOINTS (/USERS/<ID>)

3. REST(FUL) API - USAGE
GET …/users/1
{
"id":1,
"name":"Johnny",
"surename":"Hashoul",
"edited":"2014‐12‐20T20:18:48.516Z"
}

4. REST(FUL) API - USAGE (CONT’D)
Fetching comment data
GET …/users/posts
GET …/users/<postId>/comments
GET …/users/<postId>/<commentId>likes

5. GRAPHQL
Query Language created by
Facebook (2012)
Provides common interface
for data fetching and
manipulation
Natural way to describe data
requirement
Flexibility and efficiency in
mind

6. DATA
FETCHING

7. DATA
FETCHING

8. GRAPHQL
GraphiQL Demo

9. WHY GRAPHQL
No more Over- and Underfetching
 Returns more than fixed data structure
 Get the exact required fields
 Prevents underfetching

10. THANK YOU!