Decision#d1
Removed Redis and Sidekiq for GoodJob on the existing Postgres database, to cut cost and parts
- 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