Re:GoodJob – a Postgres-based ActiveJob back end for Ruby on...
by bdcravens on Thursday July 23, 2020 @03:04PM
(#23931012)
In this post, I noticed comparison with other job libraries, but not Sidekiq, the most popular one. Why?
[ Parent
| on HN ]
Re:GoodJob – a Postgres-based ActiveJob back end for Ruby on...
by sideofbacon on Thursday July 23, 2020 @06:03PM
(#23932932)
GoodJob author here. The reason is that I don't have any production experience with Sidekiq.
My target right now is someone, like myself, who would typically spin up a new project with delayed_job or que, and provide a better alternative with GoodJob.
Maybe in the future I'll do some more research on understanding why someone might switch from a Sidekiq/Redis to not-Redis.
Re:GoodJob – a Postgres-based ActiveJob back end for Ruby on...
by geoffharcourt on Thursday July 23, 2020 @04:18PM
(#23931788)
I think they specifically wanted to compare themselves to queue systems that use the database as the storage for queued jobs.