search

DelveFore / ignite-hydrogen

[Coming Soon...] | Ignite your creative idea with Hydrogen and start off with a BANG. Hydrogen builds a framework with tools and services that does the redundant work for you.
MIT License
0 stars 0 forks source link

Doc/graphql #41

Closed JonnoKiwi closed 3 years ago

JonnoKiwi commented 4 years ago

Apart of progress plan "Explaining GraphQL vs RESTful"

JonnoKiwi commented 4 years ago

Also, @JonnoKiwi would be good to give a pro and con for both.

I've added my conclusion that is listing some pros and cons

johntimothybailey commented 4 years ago

@JonnoKiwi Also, let's get this in docs/http-api-integration with docs/images/graphql-vs-restful.png

JonnoKiwi commented 4 years ago

To be super clear the quote below is wrong

“designing a RESTful system requires creating endpoints for each action”

  • [POST] /users
  • [ GET ] /users
  • [ PATCH ] /users

are all one “endpoint” with three different verbs. Now you may have three different Controllers (see Laravel for an example)

I've addressed this comment and changed the wording.

I've also relocated this writing and the image