"I'm the CTO of a Growing Rails Startup" Ask Me Anything

1. wisper

   1 6 3,301 4.2 Ruby

   A micro library providing Ruby objects with Publish-Subscribe capabilities

   

   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.

2. Judoscale

   judoscale.com featured

   Save 47% on cloud hosting with autoscaling that just works. Judoscale integrates with Rails, Sidekiq, Solid Queue, and more to make autoscaling easy and reliable. Save big, and say goodbye to request timeouts and backed-up job queues.

   

3. Interactor

   2 18 3,406 5.7 Ruby

   Interactor provides a common interface for performing complex user interactions.

   

   We don't do too many things The Rails Way™ anymore. We tend to use the Interactor pattern using the aptly named gem. We use Wisper to broadcast events instead of using AR callbacks. We use Pusher for websockets because we broadcast millions of events per day and ActionCable just can't keep up.

4. graphql-batch

   3 3 1,426 4.8 Ruby

   A query batching executor for the graphql gem

   

   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.

Suggest a related project