DEV Community

Cover image for GraphQL vs REST -  Conclusion

GraphQL vs REST - Conclusion

tbaveja on June 28, 2021

Often developers tend to feel a constant pull from REST while using GraphQL and vice-versa because of their similarities and functionalities, throu...
Collapse
 
baohx profile image
Gordon Forsythe

Just want to mention the many built-on-rest protocols like Odata, HAL, HATEOS, JSON-LD, and JSON-API. Most of these take care of all of the arguments for graphql, while still remaining RESTful and utilizing all of the wonderful functionality provided by standard browser usage like caching. Odata especially is pretty awesome in my experience, and still allows you to request a very specific structure of data.

Collapse
 
leob profile image
leob

That's a great comment - people often think that it's a contest between simple & low-level REST on the one hand, and complex/sophisticated GraphQL on the other hand, but you're right to point out that it's not as black and white as that, and that there's a middle ground!

Collapse
 
tbaveja profile image
tbaveja

Thanks for reading the post !
I just googled these terms and found interesting. Thanks for sharing the knowledge, it will surely help :)

Collapse
 
nullvoxpopuli profile image
NullVoxPopuli • Edited

Rest and graphql shouldn't be comparable.
It's like comparing low level sockets to HTTP

Why not compare something more apples to apples like { json:api } and GraphQL?

Collapse
 
tbaveja profile image
tbaveja • Edited

Hey, I compared as both can communicate with a server and retrieve data and accomplish the same task as I mentioned in similarities.
Although, I like your POV of comparing graphql with { json:api } but most of the people are replacing REST with graphql in indsutry so I thought I should throw some light on graphql vs REST so that people can make better choice.
And, I would love to hear your experience on json:api :)

Anyways, thanks for reading the post and sharing your knowledge. It will surely help :)

Collapse
 
minikothari profile image
mini kothari

Very informative

Collapse
 
tbaveja profile image
tbaveja

Thank You :)

Collapse
 
omriyahoo profile image
Omri Ratson

In the "Why Rest" part you can eliminate points 1 and 2 by implementing key-values pair of the server for key - "name of the query" and in the server will be the value - "actual implementation of the query.
and only responed to this keys provided.
Of course you can provide paramaters so it's kinda of like calling a method on the server, you don't really care what's in the method, only the parameters and what the method returns.
You can validate as well the parameters to prevent overloading the server.
Hope it helps...

Collapse
 
arvindpdmn profile image
Arvind Padmanabhan

Good to know where REST might still be useful over GraphQL. Also see migrating from REST to GraphQL: devopedia.org/rest-api-to-graphql-...

Collapse
 
tbaveja profile image
tbaveja

Thanks for reading the post !
I saw the article and found interesting. Thanks for sharing your knowledge :)
Also I noticed you're founder of devopedia. It feels good when someone like you read and appreciate the post. Thanks ☺️

Collapse
 
arvindpdmn profile image
Arvind Padmanabhan

You can also write on Devopedia platform. Given your background, you can write an article on "MERN Stack"

Thread Thread
 
tbaveja profile image
tbaveja

Thanks. Yes, I will explore and try to write few on Devopedia as well :)

Collapse
 
seanb33 profile image
Sean .

Nice article, I enjoyed it quite a bit!

Collapse
 
tbaveja profile image
tbaveja • Edited

Thank You ! Glad to hear that. I am planning to write next blog on the implementation of same i.e. implementation in graphql vs REST. I hope you'll like that too...
Also, in case of any suggestion, I would love to hear that :)

Collapse
 
seanb33 profile image
Sean .

I will surely look forward to that too! keep up the great work

Thread Thread
 
tbaveja profile image
tbaveja

Thanks. will share the link here :)

Collapse
 
sefrem profile image
sefrem

In my experience there is single to no advantages in using Graphql over Rest on small to medium projects. In only brings complexity.

Collapse
 
tbaveja profile image
tbaveja

Oh okay, I am going to post a new blog on implementing the listed features in graphql vs REST in around 1 week. I will read more on the same. BTW, thanks for reading :-)

Collapse
 
diegoguevara profile image
Diego Guevara

I had the experience in a real project, in this project we use GraphQL only for html reports and REST for all other interactions

Collapse
 
tbaveja profile image
tbaveja

Thanks for reading and sharing your experience :-)

Collapse
 
reachsuman profile image
reachsuman

Very useful blog post, thanks for sharing it

Collapse
 
tbaveja profile image
tbaveja

You're welcome ! Thanks for reading :)

Collapse
 
alex_xu profile image
MrXujiang

very instesting

Collapse
 
tbaveja profile image
tbaveja

Thanks !

Collapse
 
nipun profile image
Nipun Sood

Very informative 👍

Collapse
 
tbaveja profile image
tbaveja

Thanks buddy !

Collapse
 
namanbansal profile image
Naman Bansal

Amazing! It was a one of the good reads!
Thanks for sharing this.

Collapse
 
tbaveja profile image
tbaveja

Thanks for reading bro !

Collapse
 
experiencenote profile image
ExperienceNote

Nice one👍

Collapse
 
tbaveja profile image
tbaveja

Thanks buddy :)

Collapse
 
tbaveja profile image
tbaveja

Thanks for reading the post and sharing your experience !
I started working on GraphQL few months back :)

Collapse
 
anmolchopra69 profile image
Anmol Chopra

Awesome !! Insightful for me.

Collapse
 
tbaveja profile image
tbaveja

Thanks buddy :)

Collapse
 
moyohussein_92 profile image
Hussein AbdulQohar

Very informative. Know your weaknesses and your strengths.

Collapse
 
tbaveja profile image
tbaveja

Thanks buddy !
Yes, I agree, only then you'll be able to make productive decisions for your project.

Collapse
 
djnitehawk profile image
Dĵ ΝιΓΞΗΛψΚ

personal opinion...
graphql = yuck
🤪

Collapse
 
tbaveja profile image
tbaveja

Hahaha, sometimes it is 😄
But sometimes GraphQL is the best fit 😝
Anyways, thanks for reading the post 😌

Collapse
 
vladi160 profile image
vladi160

The whole "why GraphQL" section is the same and for REST.

Collapse
 
tbaveja profile image
tbaveja

Same as in ?

Collapse
 
vladi160 profile image
vladi160

Same as in the REST API.

Collapse
 
serusko profile image
Info Comment hidden by post author - thread only accessible via permalink
Serusko

1001 article ...... poor arguments, thank you for spam, i dont know why i got notification for this...

Some comments have been hidden by the post's author - find out more