GQLi
Ruby GraphQL Client for Humans (by contentful-labs)
graphql-batch
A query batching executor for the graphql gem (by Shopify)
Our great sponsors
| GQLi | graphql-batch | |
|---|---|---|
| 0 | 3 | |
| 210 | 1,402 | |
| 0.5% | 0.2% | |
| 0.0 | 5.2 | |
| over 1 year ago | 11 days ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GQLi
Posts with mentions or reviews of GQLi.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning GQLi yet.
Tracking mentions began in Dec 2020.
graphql-batch
Posts with mentions or reviews of graphql-batch.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-07.
-
The GraphQL N+1 Problem and SQL Window Functions
After recognizing the problem, we brainstormed options to offload some of the work onto the database server to ultimately reduce the Rails application’s memory consumption. One particularly promising avenue involved SQL window functions. After deciding to pursue SQL window functions, we started our work by considering the WindowKeyLoader example described in the graphql-batch repository.
-
N+1 problem will never be an issue with N1Loader gem
Interesting, I've just been researching Dataloader implementations for Ruby and have between trying to decide between GraphQL::Dataloader, graphql-batch and BatchLoader. I'll give this a look as well. Can you also make API calls inside the loaders?
-
"I'm the CTO of a Growing Rails Startup" Ask Me Anything
This is mainly addressed in the last thing but we cache pretty heavily on our REST APIs and for GraphQL we use the graphql-batch gem pretty heavily. Those two things can go a long way. Make sure you're using an APM like Scout to keep an eye on things and then debug the outliers.
What are some alternatives?
When comparing GQLi and graphql-batch you can also consider the following projects:
graphql-client - A Ruby library for declaring, composing and executing GraphQL queries
graphql-guard - Simple authorization gem for GraphQL :lock:
moql - Mock GraphQL server for fast reliable integration tests.
Koala - A lightweight Facebook library supporting the Graph, Marketing, and Atlas APIs, realtime updates, test users, and OAuth.
BatchLoader - :zap: Powerful tool for avoiding N+1 DB or HTTP queries
Spree Commerce - A headless open source e-commerce platform for global brands
Interactor - Interactor provides a common interface for performing complex user interactions.
RocketJob - Ruby's missing background and batch processing system