rails-extension-power-pack
good_job
Our great sponsors
| rails-extension-power-pack | good_job | |
|---|---|---|
| 1 | 26 | |
| 11 | 1,737 | |
| - | - | |
| 10.0 | 8.8 | |
| 9 months ago | 7 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.
rails-extension-power-pack
-
vscode suggestions
Andrew Mason's extension pack - https://github.com/andrewmcodes/rails-extension-power-pack
good_job
-
Watching for changes to DB by another app
In this case I would try to set up tcn (a Postgres extension) and a trigger that inserts a job in a goodjob jobs table. https://github.com/bensheldon/good_job is like sidekiq but uses Postgres as a queue.
-
How do you schedule jobs far out in advanced?
Check out https://github.com/bensheldon/good_job
- Ask HN: Companies of one, what is your tech stack?
- GoodJob v3 released: multithreaded, Postgres-based ActiveJob adapter
-
Newest way to handle Cron Jobs?
You say elsewhere that you don't want another service running for background jobs, but if you're running your app on Postgres I'd say look into GoodJob.
-
What’s the best way to test a gem that integrates with Rails?
I just opened an issue on GoodJob about turning it into a mountable engine solely if you wanted to continue that discussion: https://github.com/bensheldon/good_job/issues/543
You're welcome to check out how GoodJob is structured: https://github.com/bensheldon/good_job
-
Delayed Job vs. Sidekiq: Which Is Better?
I've been using Sidekiq for years, rock solid and no complaints.
However, this recent addition to the space seems to be gaining traction and appears to have an excellent feature set -
-
Why does rails have a tradition of queuing background jobs in a separate NoSQL store, when both the queueing controller and the job class tend to hammer the main database anyway?
GoodJob is an attempt at this using just Postgres. Seems pretty good. https://github.com/bensheldon/good_job
If I were using Postgres, I'd consider using Good Job for the very reason you state. In fact, even using MS SQL, I still tend to use Delayed Job for that same simplicity, but it's very plain to see how much extra overhead this costs. To check for work, a query happens against the jobs table. To queue work, an insert happens. This creates a lot of db work, and unnecessary processing delay when in Redis, it would just be "I'll hang tight here until you tell me there's something to do."
What are some alternatives?
sidekiq-throttled - Concurrency and threshold throttling for Sidekiq.
Sidekiq - Simple, efficient background processing for Ruby
Delayed::Job - Database based asynchronous priority queue system -- Extracted from Shopify
Que - A Ruby job queue that uses PostgreSQL's advisory locks for speed and reliability.
Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
sidekiq_alive - Liveness probe for Sidekiq in Kubernetes deployments
Karafka - Ruby and Rails efficient Kafka processing framework
aws-sdk-rails - Official repository for the aws-sdk-rails gem, which integrates the AWS SDK for Ruby with Ruby on Rails.
Sidekiq::Undertaker - Sidekiq::Undertaker allows exploring, reviving or burying dead jobs.
pg-boss - Queueing jobs in Node.js using PostgreSQL like a boss
worker - High performance Node.js/PostgreSQL job queue (also suitable for getting jobs generated by PostgreSQL triggers/functions out into a different work queue)
Backburner - Simple and reliable beanstalkd job queue for ruby