Clockwork
good_job
Our great sponsors
Clockwork | good_job | |
---|---|---|
2 | 36 | |
535 | 2,446 | |
- | - | |
0.0 | 9.3 | |
6 months ago | 5 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Clockwork
-
Newest way to handle Cron Jobs?
https://github.com/Rykian/clockwork always worked well when I have used it in the past.
-
Any idea how can we convert the string time to utc in ruby.
Unless you have very specific requirements that preclude this, you might want to run this task as a background job (e.g. Sidekiq worker) instead of as a rake task. This is a little bit of an opinion. There isn't one right way (indeed, that's one of the best things about Ruby). But in my career I've usually seen rake tasks used for things that need to be performed infrequently, and not as part of normal system operation. For things that need to be performed at regular intervals, and are part of the normal operation of the app, I usually see them set up as scheduled background jobs. You can use a background job gem (Sidekiq is wildly popular; Resque is another good one) and combine it with a scheduler (I'm personally a fan of the Clockwork gem but there are others out there).
good_job
-
solid_queue alternatives - Sidekiq and good_job
3 projects | 21 Apr 2024
This is the most direct competitor of good_job in my opinion.
-
Tuning Rails application structure
Once we are done with default gems, should we look into something we usually use? That's jwt because we need session tokens for our API. Next comes our one and only sidekiq. For a long period of time it was the best in town solution for background jobs. Now we could also consider solid_queue or good_job. In development and testing groups we need rspec-rails, factory_bot_rails and ffaker. Dealing with money? Start doing it properly from the beginning! Do not forget to install money-rails. Once everything is added to the Gemfile do not forget to trigger bundle install.
-
Postgres as Queue
In the world of Ruby, GoodJob [0] has been doing a _good job_ so far.
[0] - https://github.com/bensheldon/good_job
-
Choose Postgres Queue Technology
For Rails apps, you can do this using the ActiveJob interface via
https://github.com/bensheldon/good_job
Had it in production for about a quarter and it’s worked well.
-
Pg_later: Asynchronous Queries for Postgres
Idk about pgagent but any table is a resilient queue with the multiple locks available in pg along with some SELECT pg_advisory_lock or SELECT FOR UPDATE queries, and/or LISTEN/NOTIFY.
Several bg job libs are built around native locking functionality
> Relies upon Postgres integrity, session-level Advisory Locks to provide run-once safety and stay within the limits of schema.rb, and LISTEN/NOTIFY to reduce queuing latency.
https://github.com/bensheldon/good_job
> |> lock("FOR UPDATE SKIP LOCKED")
https://github.com/sorentwo/oban/blob/8acfe4dcfb3e55bbf233aa...
-
Noticed Gem and ActionCable
The suggestion from /u/tofus is a good one. If you are already using redis as your ActionCable adapter I would use sidekiq. If not and you're using postgres I would consider https://github.com/bensheldon/good_job
-
Introducing tobox: a transactional outbox framework
Probably worth mentioning that aside from delayed_job there are at least two more modern alternatives backed by the DB: Que and good_job.
-
Sidekiq jobs in ActiveRecord transactions
Good article. Sidekiq is a good, well respected too. However if you are starting out I would recommend not using it, and instead choosing a DB based queue system. We have great success with que, but there are others like good_job.
-
Mike Perham of Sidekiq: “If you build something valuable, charge money for it.”
Sidekiq Pro is great, we're paying for it! 10k a year I think.
But for people who are interested in alternatives, I'd also suggest Good Job (runs on Postgresql).
https://github.com/bensheldon/good_job
-
SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue
I'm the GoodJob author. Here's the class that is responsible for implementing Postgres's LISTEN/NOTIFY functionality in GoodJob:
https://github.com/bensheldon/good_job/blob/10e9d9b714a668dc...
That's heavily inspired by Rail's Action Cable (websockets) Adapter for Postgres, which is a bit simpler and easier to understand:
https://github.com/rails/rails/blob/be287ac0d5000e667510faba...
Briefly, it spins up a background thread with a dedicated database connection and doings a blocking Postgres LISTEN query returns results, and then it forwards the result to other subscribing objects.
What are some alternatives?
Whenever - Cron jobs in Ruby
Sidekiq - Simple, efficient background processing for Ruby
Sidekiq-Cron - Scheduler / Cron for Sidekiq jobs
sidekiq-throttled - Concurrency and rate-limit throttling for Sidekiq
sidekiq-scheduler - Lightweight job scheduler extension for Sidekiq
Que - A Ruby job queue that uses PostgreSQL's advisory locks for speed and reliability.
rufus-scheduler - scheduler for Ruby (at, in, cron and every jobs)
Delayed::Job - Database based asynchronous priority queue system -- Extracted from Shopify
resque-scheduler - A light-weight job scheduling system built on top of Resque
Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
minicron - 🕰️ Monitor your cron jobs
Sidekiq::Undertaker - Sidekiq::Undertaker allows exploring, reviving or burying dead jobs.