Skip to content

Instantly share code, notes, and snippets.

@haldarmahesh

haldarmahesh/graphql-vs-rest.csv

Last active August 28, 2020 20:53
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save haldarmahesh/fcf71ee7de7eb11866e1ecfc92b6a588 to your computer and use it in GitHub Desktop.
Save haldarmahesh/fcf71ee7de7eb11866e1ecfc92b6a588 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
graphql-vs-rest.csv
REST APIs GraphQL
one URL serves only one request which leads to 100s of URL to maintan One URL to serves every request
Multiple roundtrip to get various kinds of data Single trip to get various combinations of data
Unwanted data travel from server to client (Wastage of bandwidth) Only required data is travelled which make response light and minimum number
No flexibility Much more flexible
Keeps Backend and frontend team tightly coupled Backend and frontend team are loosely coupled
Change in structure of APIs needs the client to change as well Change in structure of API is not needed in client side
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment