I think REST API is very lower level, and cannot compare to GraphQL.

Pacharapol Withayasakpunt

Aug 9

I learnt today that there are actually three things or more...

graphql.org/learn/serving-over-http/

What is the difference between HTTP and REST?

Feb 3 '10 Comments: 7 Answers: 12

312

After reading a lot about the differences between REST and SOAP, I got the impression that REST is just another word for HTTP. Can someone explain what functionality REST adds to HTTP?

Note: I'm not looking for a comparison of REST versus SOAP.

Update: Thanks for your answers…

Open Full Question

It feels like GraphQL and REST API are actually apples and oranges.

This seems to be a correct answer.

hasura.io/blog/rest-view-of-graphql/

I have seen (but never tried) OData, which seems to be focused on GET request and querystrings (and of course has URL length limits.)

I think GraphQL is very daring, in that it encourages using POST to query data, which is controversial, when talking about REST API. (It seems to compensate with different caching mechanisms...)

REST API using POST instead of GET

Oct 28 '13 Comments: 6 Answers: 8

74

Let's assume a service offers some funcionality that I can use like this:

GET /service/function?param1=value1&param2=value2

Is it right to say that I can use it with a POST query?

POST /service/function { param1 : value1, param2 : value2 }

Are these two queries the same? Can I use the second…

Open Full Question

Of course, I can use POST requests with a well-defined JSON schema as well, but it probably will never be as secure, nor standardized, as GraphQL...

https://www.howtographql.com/advanced/4-security/

GraphQL is not only for fetching. It can do mutations as well, but why?

https://graphql.org/learn/queries/#mutations

What are you thoughts, knowledge of history, and recommendations?