Developer-roadmap: why not includes the GraphQL?

Created on 18 Feb 2019 · 6Comments · Source: kamranahmedse/developer-roadmap

why not includes the GraphQL?

I think it will be the trending of new API development, just like GitHub version 4.

https://github.com/topics/github-api
https://developer.github.com/

Source

xgqfrms

👍6 🎉3 👀2 🚀2 😄2

Most helpful comment

It should be in backend as well.

smoke on 21 Feb 2019

👍11

All 6 comments

In which chart? Frontend? Backend? DevOps?

Firefishy on 19 Feb 2019

Frontend

xgqfrms on 20 Feb 2019

👍1

It should be in backend as well.

smoke on 21 Feb 2019

👍11

Both side Back and Front and Apollo as favorite tech. After maybe Relay.... others (I don't know others well o_O)

Bastorx on 4 Mar 2019

😄1 👍1

This has been fixed and will be published in the coming release. Thank you 🙏

kamranahmedse on 3 Jan 2020

I daresay that in Backend, GraphQL should be in "Learn about APIs" at this point, given the rate of adoption. REST should definately be learned always as a prerequesite to implementing GraphQL over HTTP, so the "learn at any time" legend key would remain, though GraphQL has a much broader scope and application than HTTP webservice APIs, all of it's applications would fall under the broad category of "APIs".

Should I open a new ticket?

that said, the place where it sits still makes sense, since it tends to be at the front of a "backend" stack (for example, to stitch service interfaces together into a common schema)