brblck

5 ms·

1. 1.▲
   by brblck 10y ago

   Needs more black.
2. 2.▲
   by brblck 10y ago

   Yup. That's something we can handle internally, under the hood to batch database requests into a single query for all edges. This problem is actually easier to solve in GraphQL then it is with a traditional REST API.
3. 3.▲
   by brblck 10y ago

   I theory a GraphQL API can operate verison-less utilizing things like deprecation notices and field aliasing to smooth over any rough edges. Once we see calls on a certain thing reach zero and sustain that level, we can actually remove it
4. 4.▲
   by brblck 10y ago

   One really great feature of GraphQL (which GitHub doesn't support yet in this alpha, but we plan to) is the ability to store queries for execution later. This lets us optimize and plan for the data and volume of requests being generate
5. 5.▲
   by brblck 10y ago

   This definitely enables a lot of opportunity to do both smarter querying and smarter caching on the back-end. While you can indeed perform larger, more complex requests, GraphQL by nature forces queries to explicitly ask for everything you
6. 6.▲
   by brblck 10y ago

   Special shout out to the open-source contributors and members of the community who helped us build this: https://github.com/rmosolgo/graphql-ruby https://github.com/shopify/graphql-batch https:&#