I've been using Sidekiq for years, rock solid and no complaints.
However, this recent addition to the space seems to be gaining traction and appears to have an excellent feature set -
However, this recent addition to the space seems to be gaining traction and appears to have an excellent feature set -
As long as you stick to pure ActiveJob features it really shouldn't be too difficult to scale from in memory based queue to PostgresSQL backed Good Job and then to Redis backed Sidekiq if and only if you need to.
> 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.
Perhaps you could address my point? Open source background job software that isn't reliable by default? That makes sense?