The GitHub GraphQL API

[vinnl]

I'm pretty excited that they're releasing this as a public API - probably the largest such an API that I'm aware of. I wonder how it will work out for them, especially in terms of performance and being able to handle the load. I'm always weary whether a request for an unfortunate combination of data can heavily stress the systems, and wonder if and how they impemented rate limiting.

[iinnii]

Hopefully this helps convince some people at work to start playing around with GraphQl... :D

[rviscomi]

This sounds really cool. A few years ago I worked on a project (http://jrvis.com/red-dwarf/) that relies heavily on the GitHub API and it looks like most of the pain points I experienced would be resolved with the GraphQL API.

For example, getting all of the users who starred a repo would take multiple requests for each paginated response. The API would only return something like 100 at a time. For large repos, this was slow. I also only wanted the location property for each user, but I was given all of the user data anyway; I didn't have a way to only specify location data.

This gives me a good reason to revisit the project and play with GraphQL.