DEV Community

loading...

Discussion on: 4 reasons why you should use GraphQL over REST APIs

Collapse
siddhantk232 profile image
Siddhant Kumar

I think the title is wrong, it should be more like "difference b/w graphql and rest". You can't just say to stop using one over the other. Both have their own benefits.
Also, the content of this post is more like telling the difference.

Collapse
janpauldahlke profile image
jan paul

on point! ty

Collapse
highcenburg profile image
Vicente G. Reyes

His article, his rules. He wants the title to be like that, let him name the article like that.

Collapse
clivend profile image
clivend

and keep on feeding the click-bait culture? Siddhant just made a senseful suggestion

Thread Thread
highcenburg profile image
Vicente G. Reyes

While I'm not in the position to say this, but he might be writing for his future self.

Thread Thread
clivend profile image
clivend

you can save a note on your laptop for that. Here many junior developers come to look for resources, and in this case they can be fooled and confused and reach to GQL even to ping a server just because "stop using REST for APIs"

Thread Thread
highcenburg profile image
Vicente G. Reyes

Just let it be, man.

Thread Thread
blessingartcreator profile image
Blessing Hirwa Author

I get you point, but in my conclusion I said that you must do a research before starting your project. GraphQL is not always the best solution.

Collapse
thesanjeevsharma profile image
Collapse
blessingartcreator profile image
Blessing Hirwa Author

My point here was to show how Graphql can make your work more easier. I also said that Graphql is not always the best solution.

Collapse
oliverleitner profile image
Oliver Leitner

i hear you, it helped me already alot...
i usually draw the line at the size of the thing im working at. for small stuff a simple query string to the interface is often enough.

Thread Thread
blessingartcreator profile image
Blessing Hirwa Author

yeah, sometimes it's not appropriate to use GraphQl for small tasks as for REST works well on small tasks.

Collapse
peterdonovan profile image
Peter Donovan

The title of your article is literally, "4 reasons why you should use GraphQL over REST APIs" and your slug is, "stop-using-rest-for-apis-53n".

Also, GraphQL has many drawbacks, none of which you really mentioned. What about the N + 1 problem? Or having to use and/or implement DataLoader?

Thread Thread
blessingartcreator profile image
Blessing Hirwa Author

In the middle of the post I said that it is difficult to implement caching and that it's not always the best solution.

Collapse
muhyilmaz profile image
MUHAMMED YILMAZ

he changed it now :).

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