News for hackers. Stuff that matters.
Re:Delayed Job vs. Sidekiq by waffle_maniac on Wednesday February 16, 2022 @09:48AM (#30360618)
Without the pro version it's not reliable:

> If a Sidekiq process crashes while processing a job, that job is lost. [0]

We use Sidekiq Pro at work but I find it unfortunate that reliability is a pro feature. It's really hard to tell a product owner: Yeah, we might lose a few jobs once in a while.

[0] https://sidekiq.org/products/pro.html

Re:Delayed Job vs. Sidekiq by aaronbrethorst on Wednesday February 16, 2022 @11:30AM (#30362068)
Seems like a good reason to pay Mike.
Re:Delayed Job vs. Sidekiq by jdc0589 on Wednesday February 16, 2022 @02:27PM (#30364559)
agree. its not a lot of money, or it didn't used to be last time I looked. If your org relies heavily on it just pay
Re:Delayed Job vs. Sidekiq by aaronbrethorst on Wednesday February 16, 2022 @02:31PM (#30364597)
I just looked this up. It's $995/year, or approximately 4% of the fully loaded cost of an FTE software engineer at most companies. i.e. about 3 weeks of a developer's time.
Re:Delayed Job vs. Sidekiq by waffle_maniac on Wednesday February 16, 2022 @03:28PM (#30365247)
I understand paying extra for niche features. Isn't reliability a core feature of background job software?
Re:Delayed Job vs. Sidekiq by waffle_maniac on Wednesday February 16, 2022 @03:30PM (#30365270)
We do pay for it.

Perhaps you could address my point? Open source background job software that isn't reliable by default? That makes sense?