graphql-batch
wisper
Our great sponsors
graphql-batch | wisper | |
---|---|---|
3 | 6 | |
1,402 | 3,226 | |
0.5% | - | |
5.2 | 1.5 | |
16 days ago | 21 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
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.
graphql-batch
-
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.
wisper
-
Publish/Subscribe with Sidekiq
Wisper: A Ruby gem providing a decoupled communication layer between different parts of an application -> I personally dislike wisper. I used it in the past and dislike the way of defining subscribers in a global way. I wanted topics to be arbitrary and each class to define what to subscribe for itself.
-
OOP vs. services for organizing business logic: is there a third way?
Wisper – the Publish-Subscribe design pattern
-
Event Store with Rails
I haven't used it, but we're also considering it in our app for quite some time. Our main issue is mostly that our codebase is super coupled, especially some older code, and using events as a means of communication between different modules of the app can be nice way of decoupling things. I think this is the most common usecase, and for this you don't necessarily even need to persist the events, and also something like wisper might be useful https://github.com/krisleech/wisper.
-
Rails Google Cloud PubSub options
Whisper (not updated since 2020)
-
How to avoid if/else with different ramifications
I would use events. Every services broadcast its results and everything that needs to listen for them. It also great to decouple dependencies between services. I like the Wisper gem : https://github.com/krisleech/wisper
-
"I'm the CTO of a Growing Rails Startup" Ask Me Anything
We follow the interactor pattern to store our business logic. So we mainly have skinny controllers, skinny models and then interactors. We also don't use ActiveRecord callbacks very much, we primarily use Wisper to broadcast events and then various domains can subscribe to the events they care about and respond accordingly.
What are some alternatives?
Rails Event Store - A Ruby implementation of an Event Store based on Active Record
Interactor - Interactor provides a common interface for performing complex user interactions.
graphql-guard - Simple authorization gem for GraphQL :lock:
graphql-client - A Ruby library for declaring, composing and executing GraphQL queries
Rocketman - 🚀 Rocketman help build event-based/pub-sub code in Ruby
Cells - View components for Ruby and Rails.
Light Service - Series of Actions with an emphasis on simplicity.
Waterfall - A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!
Amoeba - A ruby gem to allow the copying of ActiveRecord objects and their associated children, configurable with a DSL on the model
PageletRails - Improve perceived performance of your rails application with minimum effort
u-service - Represent use cases in a simple and powerful way while writing modular, expressive and sequentially logical code.
Smart Init - Simple service objects in Ruby - A simple gem for eliminating Ruby initializers boilerplate code, and providing unified service objects API