graphql VS Sidekiq

My memory is fuzzy, but...

1. all data flow through the rails app (no pre-signed s3 upload or download links for direct uploading).

2. no support for CDNs (I think newer rails versions added support)

3. blobs and attachments were unnecessary abstractions.

3a. Querying was annoying and easy to add n+1 queries.

3b. Images are moderated and it was unclear where to put the moderation metadata (on blobs? attachments? create a new table? why so many tables?). Accessing the data was annoying (you need extra joins).

4. GraphQL gem didn't support it: https://github.com/rmosolgo/graphql-ruby/issues/1777

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.

If you're comfortable on the react/client side with graphql, I'd highly recommend plugging in https://graphql-ruby.org/

We use GraphQL, and Ruby GraphQL doesn't allow you to stream the result, it buffers it before sending back the request and there are no alternative. See my issue https://github.com/rmosolgo/graphql-ruby/issues/3969 -- Sadly there is only one library for GraphQL in Ruby.

graphql-ruby is a Ruby gem that implements the GraphQL specification and functionalities.

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:

If you do go the API route though, strongly consider using GraphQL with the (graphql-ruby)[https://graphql-ruby.org/] gem.

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

When it comes to implementing a GraphQL server in Rails, one can use the excellent GraphQL Ruby gem.

Hi there! I want to show off a little feature I made using hanami, htmx and a little bit of redis + sidekiq.

I'd say Sidekiq is the top competitor here.

There's something wrong at Redislabs, it took them over a year to get RESP3 rolled out into their hosted service, you'd expect a rollout of that to be a bit quicker when they're the owner of Redis.

It affected us when upgrading Sidekiq to version 7, which dropped support for older Redis, and their Envoy proxy setup didn't support HELLO and RESP3: https://github.com/sidekiq/sidekiq/issues/5594

That depends on how the `maxmemory-policy` is configured, and queue systems based on Redis will tell you not to allow eviction. https://github.com/sidekiq/sidekiq/wiki/Using-Redis#memory (it even logs a warnings if it detects your Redis is misconfigured IIRC).

Sidekiq https://sidekiq.org/: This one started as an open source project, once it got enough traction, the developer made a premium version of it, and makes money by selling licenses to businesses.

Sidekiq will drop in-progress jobs when a worker crashes. Sidekiq Pro can recover those jobs but with a large delay. Sidekiq is excellent overall but it’s not suitable for processing critical jobs with a low latency guarantee.

https://github.com/sidekiq/sidekiq/wiki/Reliability

> I'm not sure feature withholding has traditionally worked out well in the developer space.

I think it's worked out well for Sidekiq (https://sidekiq.org). I really like their model of layering valuable features between the OSS / Pro / Enterprise licenses.

I was studying Sidekiq's page on rate limiters. The first type of rate limiting mentioned is the concurrent limiter: only n tasks are allowed to run at any point in time. Note that this is independent of time units (e.g. per second), or how long they take to run. The only limitation is the number of concurrent tasks/requests.