You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe one thing missing from the current graphql-go library is the ability to either defer query execution to batch queries or some method of reducing complex queries so you aren't taking such a performance hit while retrieving items from a database.
Now with the current state of GraphQL there seems to be a couple different ways to do this, I think we can get our own discussion going about how to implement similar functionality in Go and how such an API should look. Once I have a little more of an idea about a finalized API I have no problem sending in a pull request for further review.
I'll link here some current patterns to aid in the discussion:
Scala's primary GraphQL library Sangria has probably the largest implementation of performance enhancing patterns. They have an entire section on deffered values and resolvers. Essentially they have per type batched deferred values so you can perform say, one SQL query to fetch all these values and have the framework still marshall the proper results.
Shopify has made their own library for batching GraphQL requests in Ruby. It can be located here.
Here is the current discussion on the main graphql repository for reducing their executer queries: graphql/graphql-js#26.
The text was updated successfully, but these errors were encountered:
I believe one thing missing from the current graphql-go library is the ability to either defer query execution to batch queries or some method of reducing complex queries so you aren't taking such a performance hit while retrieving items from a database.
Now with the current state of GraphQL there seems to be a couple different ways to do this, I think we can get our own discussion going about how to implement similar functionality in Go and how such an API should look. Once I have a little more of an idea about a finalized API I have no problem sending in a pull request for further review.
I'll link here some current patterns to aid in the discussion:
Scala's primary GraphQL library Sangria has probably the largest implementation of performance enhancing patterns. They have an entire section on deffered values and resolvers. Essentially they have per type batched deferred values so you can perform say, one SQL query to fetch all these values and have the framework still marshall the proper results.
Shopify has made their own library for batching GraphQL requests in Ruby. It can be located here.
Here is the current discussion on the main graphql repository for reducing their executer queries: graphql/graphql-js#26.
The text was updated successfully, but these errors were encountered: