In our Rails application, we use the popular graphql Ruby gem to resolve GraphQL queries. When used naively, it essentially resolves queries as a depth-first tree traversal, which leads to the N+1 problem in GraphQL. - Source: dev.to / over 1 year ago
If you're comfortable on the react/client side with graphql, I'd highly recommend plugging in https://graphql-ruby.org/. Source: over 1 year ago
The next step is to add the GraphQL gem to our Gemfile; you can visit its page, graphql-ruby, for more details; now, open your Gemfile and add this line:. - Source: dev.to / about 2 years ago
If you do go the API route though, strongly consider using GraphQL with the (graphql-ruby)[https://graphql-ruby.org/] gem. Source: about 2 years ago
GraphQL saves you time designing versioned REST endpoints. It self documents. Documentation isn't optional for serious web development so this is a huge win. The rails gems have gotten really good at picking up associations as well since I looked into a couple years ago. https://graphql-ruby.org. Source: over 2 years ago
When it comes to implementing a GraphQL server in Rails, one can use the excellent GraphQL Ruby gem. - Source: dev.to / almost 3 years ago
In this write up we show you how to setup end-to-end GraphQL Subscriptions via websockets, using graphql-ruby and Pusher. Source: over 2 years ago
While working with GraphQL in Rails, there, arises a problem with uploading a file to the system. One way is to upload the file through REST API but what if we want solely in GraphQL then there is a gem to do that. ApolloUploadServer. - Source: dev.to / over 2 years ago
I just got into GraphQL a few weeks ago and so far I'm really liking what I see, especially the tooling it makes available on the front end (I use Angular), reducing boilerplate a lot. I'm using Ruby on the server side with the https://graphql-ruby.org gem. Source: over 2 years ago
While developing your GraphQL api using graphql-ruby you will probably come across the need of generating the schema definition file from the schema you defined in your code, so other front-end client would be able to consume it, or generate types automatically based on that schema. - Source: dev.to / almost 3 years ago
I've been using graphql-ruby for some time to provide an API for our frontend to consume. During that time I've hit some bumps in the road, like: - Performance: Fixed mostly by batch loading with graphql-batch - Overfetching: Clients are pretty free in fetching tons of data if you are not careful designing your schema. Source: almost 3 years ago
AppSignal supports the graphql gem for Ruby. It will instrument every GraphQL request that comes in and provide a breakdown of all events in the request. You'll be able to see how long it took to parse, validate and execute your resolvers. Events from the app's web framework and database calls are of course included in this breakdown. - Source: dev.to / almost 3 years ago
While doing basic REST APIs are sometimes a great solution and super easy (like Grape mentioned in another comment) and much faster - if this is a larger project you might want to check out https://graphql-ruby.org/ ... It makes typical asks of clients like "but I want to know all the schools that user is in and, for each school, it's email, phone and fb" much easier. It also makes fine grained security pretty... Source: about 3 years ago
TL;DR is Apollo server is a great option, as well as GraphQL-Ruby (if you want an adventure in a new language): https://graphql-ruby.org/. Source: about 3 years ago
Do you know an article comparing GraphQL Ruby to other products?
Suggest a link to a post with product alternatives.
This is an informative page about GraphQL Ruby. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.