Quick Guide to GraphQL for BackEnd & FrontEnd

GraphQL is one of those technologies which is constantly on my radar, just waiting for the right time and project to try it on.  For now, I’m just slowly moving to that target, collecting links to resources in the meantime.

Introduction & Quick Guide to GraphQL for BackEnd & FrontEnd” is a new addition to my collection.  This article, much like many others, provides a brief introduction to the technology.  And it also shows a practical example of how to design and implement GraphQL API both on the front and back ends.  I give it extra credits for mentioning GraphiQL in-browser IDE for exploring GraphQL.

GitHub GraphQL API v4

I’ve briefly mentioned before that GitHub joined the adopters of the GraphQL for their API.  Here’s the link to the full documentation and more details.

GitHub chose GraphQL for our API v4 because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and only the data you want—is a powerful advantage over the REST API v3 endpoints. GraphQL lets you replace multiple REST requests with a single call to fetch the data you specify.

Rest APIs are REST-in-Peace APIs. Long Live GraphQL.

Rest APIs are REST-in-Peace APIs. Long Live GraphQL.” is yet another look at REST vs. GraphQL for the API implementation.

I’m involved with developing quite a bit of REST APIs at work, but for now we are just trying to buy us some time.  I want to take a really long and good look at GraphQL, but I don’t think this will happen this year.  In the meantime, if you have any good GraphQL resources, please do send them my way.