Catalogue / tosbourn-2023-client-rails-jobs

A Tosbourn client's very small Rails app drops Sidekiq and Redis for a Postgres-backed job processor

Unnamed client of Tosbourn Ltd, 2023. Client Rails application background jobs.

Organisation
Unnamed client of Tosbourn Ltd
Evidence
Reported from production
System
Client Rails application background jobs
As of
2023
Source
Replacing Sidekiq with GoodJob

tosbourn.com (Tosbourn Ltd blog), published 2023-01

Architecture

A very small and simple Rails application whose background jobs go through Active Job. Its jobs had recently been moved from Sidekiq, which needs Redis, to GoodJob, which uses Postgres and can piggy-back on the existing database.

Near: moved a client's ActiveJob processor from Sidekiq | Near: piggy-back on your existing database | Near: very small and simple project

Figures, as the source states them

FigureAs statedNoteWhere
Jobs handled by the client application20 jobs per dayMaybe; at the absolute max, per the authorSection: Why we decided to move
Monthly Redis hosting cost30 dollars per monthAbout; across the client's environmentsSection: Why we decided to move

Records

Decision#d1

Removed Redis and Sidekiq for GoodJob on the existing Postgres database, to cut cost and parts

tosbourn-2023-client-rails-jobs#d1 at corpus version 74847648e25a
Chosen

The contractor replaced the client's Sidekiq job processor, which needs Redis, with GoodJob, which stores jobs in Postgres and so can reuse the database the app already has. Because of the nature of the project, they deployed without worrying about losing a job in Sidekiq.

Near: piggy-back on your existing database | Section: Why we decided to move | Near: deploy without having to worry about if

Reasoning

Mainly money: the client paid about $30 a month across environments for Redis to run at most about 20 jobs a day. Dropping Redis also simplified the stack, and GoodJob's UI, job history and search were further attractions.

Section: Why we decided to move

Outcome

The client's hosting bill fell by $30 a month, and the author's impression is that jobs run at least as quickly as they appeared to under Sidekiq; no benchmarks were run because the jobs are few and infrequent.

Section: First impressions

Reviewer's notes

The post describes no plan for draining or dual-running jobs in flight. Its warning that searchable job records may expose sensitive data is advice to readers, not a cost the team reports paying, so cost_paid is null.

The reviewer's reading, not the source's claim

The post is a contractor's account of a client's application, written shortly after the switch. It gives no team size, no database size, no time in production on GoodJob and no incident history.

The reviewer's reading, not the source's claim

Cost was a motive, not a pain that forced action; the post praises Sidekiq in general and reports no problem with it in this app.

The reviewer's reading, not the source's claim

Review

Extracted by
claude-sonnet-5-5
Human review
Not started. Status recorded on 2026-11-16.