active-job-style-guide
This Background Jobs style guide is a list of best practices working with Ruby background jobs. (by toptal)
acidic_job
Idempotent operations for Rails apps, built for ActiveJob or Sidekiq. (by fractaledmind)
active-job-style-guide | acidic_job | |
---|---|---|
1 | 2 | |
466 | 397 | |
0.2% | - | |
0.0 | 7.0 | |
8 months ago | 9 months ago | |
Ruby | ||
- | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
active-job-style-guide
Posts with mentions or reviews of active-job-style-guide.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-01-06.
-
ActiveJob: Async and Inline adapters don't execute my code?
To my best memory, when retries are exhausted, and I hope you mean Sidekiq retries, not Active Job's retries, Sidekiq raises an exception that Active Job catches and runs your error handler (that typically submits to Sentry/Rollbar). The job is moved to the Dead queue. I can't tell the details off the top of my head, the guide has an explanation why using Active Job retries with Sidekiq is a bad idea. https://github.com/toptal/active-job-style-guide#retries
acidic_job
Posts with mentions or reviews of acidic_job.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-17.
-
Organize Business Logic in Your Ruby on Rails Application
There are several workarounds for this, like the magnificent Acidic Job gem or Sidekiq Pro/Enterprise features around enhanced reliability and unique jobs. Still, if they occur, bugs related to missing jobs and/or job idempotency are hard to track down and even harder to fix.
-
Announcing sidekiq-iteration - a gem that makes your sidekiq jobs interruptible and resumable by design
I think acidic-job also covers a similar problem space with the Iterable Steps feature.
What are some alternatives?
When comparing active-job-style-guide and acidic_job you can also consider the following projects:
lambdakiq - 🔄👷 ActiveJob with SQS & Lambda
activejob-uniqueness - Unique jobs for ActiveJob. Ensure the uniqueness of jobs in the queue.
Gush - Fast and distributed workflow runner using ActiveJob and Redis
sidekiq-iteration - Make your long-running sidekiq jobs interruptible and resumable.
Sidekiq - Simple, efficient background processing for Ruby
Shoryuken - A super efficient Amazon SQS thread based message processor for Ruby
job-iteration - Makes your background jobs interruptible and resumable by design.