I learnt today that there are actually three things or more...
graphql.org/learn/serving-over-http/
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…
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/
We're a place where coders share, stay up-to-date and grow their careers.
I learnt today that there are actually three things or more...
graphql.org/learn/serving-over-http/
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…
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/