Rails Erd VS Sidekiq

I've been using a simpler version of this https://github.com/voormedia/rails-erd but it seems neat that this comes with a web app and a query language.

Graphviz

Use the rails-erd gem to generate an ERD: http://voormedia.github.io/rails-erd/

Entity Relationship Diagrams (ERDs) are super useful for visualizing databases. For an ERD example, or to see how to make one, see this gem. Though note that gem is only for rails 3-5.

You should take a look at rails-erd, it is really easy to set up and works quite well

At my work we've got a 10-year-old Rails app (originally started as Rails 3), rake stats says we're now over 100kloc (non-test). We've got a huge amount of complexity and cross-dependencies (not to mention, probably-dead code), and the majority of our test suite runtime (about 40h non-parallelized) is in cucumber because developers can't get a clear view of the level of the app they're dealing with, and I suppose don't feel they can trust the lower layers of the application. Running rails-erd on it generates the very definition of spaghetti, it's gross.

This PR fix the build

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.