Compare Sidekiq and GoodJob and define if we should change the standard

[malparty]

Why

Sidekiq now has viable & Prod-ready alternatives. GoodJob is one of them.

Why would we want to replace Sideqik? 👀

First, it requires you to have Redis, an additional infrastructure component to maintain (or pay for). Second, using Redis for job storage is prone to transactional integrity errors (we talk about this problem and the solution below, so continue reading).

---

One additional benefit of using GoodJob or SolidQueue is built-in support for recurrent jobs (cron-like). For non-Enterpise Sidekiq, you must use some third-party tool for that.

---

Source: Gemfile of dream

We might want to create a Discussion or an Engineering Initiative for this topic 🤔 This issue is just to prioritize among other work and ensure we will change the template after this discussion or initiative.

Who Benefits?

Future Projects with cheaper and easier-to-maintain infra.

[malparty]

Status progress:

• [x] POC
• [ ] Presentation

[sanG-github]

The comparison can be found on the Notion page, but haven't completed yet.

[sanG-github]

The documentation comparing GoodJob and SideKiq has been completed. Next time, I will try presenting it in the Web Chapter.

Btw, we don't need to tackle this integration, as SolidQueue (which has been inspired by GoodJob) will become the default background job management in Rails 8. 🚀

[suho]

@malparty @sanG-github just about to raise SolidQueue after watching Rails World 2024 Opening Keynote, good things coming in Rails 8.

I'm inspired by that opening keynote and will plan my work to join rails templates as a contributor 🙈

[malparty]

@suho @sanG-github we might want to follow up this thread: https://www.reddit.com/r/rails/comments/1g4ua4p/sidekiq_vs_goodjob_vs_solid_queue/

Some concerns for SolidQueue at the moment:

• Lack of middleware (to check if we even need any middleware in our current projects, I don't think so)
• Some jobs stopped without any error (only 1 report at the time of writing. Maybe it's due to a bad migration?)

Getting more people to use it first (and raise issues) might be needed before we jump to it on client projects ;-) But it's a very good news still 🚀

[suho]

@malparty We might have an initiative to set up and compare tools (sidekiq, goodjob, solidqueue), then officially use it for rails templates + mention it on Compass