Dramatiq VS Sidekiq

Using something like Dramatiq [1] with Redis, writing a background job takes minutes, and can be deployed alongside an existing Python web app. There are probably JS equivalents. I think Inngest could be a useful service, but the comparison felt off for me - it made me feel like this wasn't solving a real problem. [1] https://dramatiq.io/. - Source: Hacker News / 10 months ago

Hello everyone. We want to present you Taskiq: our new project that allows sending tasks using distributed queues. Conceptually it's similar to Celery or Dramatiq but with full asyncio and type hints support. Taskiq can send and execute async functions and has many integrations with different queue implementations. Source: about 1 year ago

I spent 3 years building a high scale crawler on top of Celery. I can't recommend it. We found many bugs in the more advanced features of Celery (like Canvas) we also ran into some really weird issues like tasks getting duplicated for no reason [1]. The most concerning problem is that the project was abandoned. The original creator is not working on it anymore and all issues that we raised were ignored. We had to... - Source: Hacker News / over 1 year ago

I have been using dramatiq lately (celery alternative) and so far I'm happy with it. Source: almost 2 years ago

If your tasks are idempotent, Dramatiq if intended for your case. https://dramatiq.io/. - Source: Hacker News / almost 2 years ago

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. Source: 5 months ago

> 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. - Source: Hacker News / 7 months ago

The code above isn't idempotent. If you run it twice, it will create two copies, which is probably not what you intended. Why is this important? Because most backend job processors like Sidekiq don't make any guarantees that your jobs will run exactly once. - Source: dev.to / 11 months ago

Relevant Patio11 comment from 2016: > We don't donate to OSS software which we use, because we're legally not allowed to. > I routinely send key projects, particularly smaller projects, a request to quote me a commercial license of their project, with the explanation that I would accept a quote of $1,000 and that the commercial license can be their existing OSS license plus an invoice. My books suggest we've spent... - Source: Hacker News / over 1 year ago

So how do we trigger such a long-running process from a Rails request? The first option that comes to mind is a background job run by some of the queuing back-ends such as Sidekiq, Resque or DelayedJob, possibly governed by ActiveJob. While this would surely work, the problem with all these solutions is that they usually have a limited number of workers available on the server and we didn’t want to potentially... - Source: dev.to / about 2 years ago