BT

Your opinion matters! Please fill in the InfoQ Survey!

GitHub GraphQL API is out of Early Access

| by Sergio De Simone Follow 5 Followers on Jun 08, 2017. Estimated reading time: 2 minutes |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

GitHub GraphQL API has recently become generally available. InfoQ has spoken with GitHub senior engineering manager Kyle Daigle.

Announced at GitHub Universe last year, GitHub GraphQL API aims to add more flexibility to GitHub API. The main advantage of GraphQL is its ability to define exactly what data are required, which makes it possible to replace multiple REST request with a single call. Additionally, GraphQL schemas are strongly typed and introspective.

InfoQ has spoken with Daigle to learn more about its evolution and future.

InfoQ: GitHub provided early access to its new GraphQL API last October. What has been the evolution of the API (V4) since? What new features were implemented, requested, or contributed? How would you describe developers’ reactions?

Kyle Daigle: Developers have been excited to use the new GraphQL API since our early access at GitHub Universe. For example, integrators are finding ways to access data more efficiently than they could before. As we build new features into GitHub, we also release those features via our GraphQL API. Developers have enjoyed being able to ask for just the data they need using the same API that our own engineers use.

InfoQ: Meanwhile, GitHub has not stopped working on REST API (V3). How do they stack up against each other? Do you foresee V3 to be superseded at some point in time?

Daigle: Right now, we’re watching how integrators and developers use the new GraphQL API to make changes and improvements to the new V4 API. We are actively moving REST API to be backed by GraphQL as well to continue to power the REST API. Over the coming months, we’ll be adding more data to the GraphQL API to bring it closer to providing the same data as the REST API.

InfoQ: Is it already possible to draw some conclusions regarding GitHub GraphQL adoption outside of GitHub? How is it delivering on its promises of better scalability, type safety, introspection, etc.?

GraphQL is seeing larger adoption within the larger technology community. GraphQL EU and GraphQL Summit have become two large, yearly events where small and larger companies talk about using GraphQL. GraphQL has allowed our integrators to build features more quickly and with more clarity around exactly what the API is providing via its type system. GitHub is committed to helping the larger GraphQL community grow and we’re excited to contribute back to the community with our experiences running the first major public GraphQL API.

To learn more about GitHub GraphQL, good starting points are its official documentation and tutorials.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT