GitHub goes to GraphQL

On May 22, GitHub announced that the next version of their API will use a technology developed by Facebook called GraphQL.

As a result, GraphQL can replace the most popular API type to date - the REST API.

The documentation for the new version of the GitHub API says:

“In version 4 of the API, GitHub is moving towards GraphQL, as this technology provides much more flexibility for integrators. The ability to accurately identify the data you need (and only those that are needed) is a great advantage compared to REST API v3. ”



“GraphQL allows you to rethink the creation and use of the API. Instead of making multiple REST requests to get the data of interest, in most cases you can only make one call. ”

We have already written quite a lot about GraphQL and are planning to create several lessons on this technology.

What to read about GraphQL:

• An article written by GitHub developer David Celis: “Give it a REST: use GraphQL for your APIs” ( 5 minutes to read )
• Javascript article: “So what’s this GraphQL thing I keep hearing about?” ( 12 minutes to read )

References:

1. Original: The steady rise of GraphQL .