with_advisory_lock
sidekiq-unique-jobs
| with_advisory_lock | sidekiq-unique-jobs | |
|---|---|---|
| 1 | 4 | |
| 613 | 1,419 | |
| 0.5% | - | |
| 6.6 | 7.9 | |
| 2 months ago | about 1 month 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.
with_advisory_lock
-
How to Avoid Race Conditions in Rails
Advisory locking is a mechanism used to prevent concurrent execution of code without necessarily locking the database table or row. In core Ruby, this is implemented using mutex. In Rails, the Ruby gem with_advisory_lock can be used to add advisory locking (mutexes) to ActiveRecord when used with MySQL or PostgreSQL.
sidekiq-unique-jobs
-
How to Avoid Race Conditions in Rails
If you use Sidekiq workers to make changes to your database, you can use SidekiqUniqueJobs to add unique constraints to Sidekiq queues. Uniqueness is achieved by acquiring locks for a hash of a queue name, a worker class, and a job's arguments. By default, only one lock for a given hash can be acquired. If an attempt to acquire a new lock is made, an exception SidekiqUniqueJobs::ScriptError is raised.
- Sidekiq - enqueue a job after a series of other jobs are finished
-
Delayed Job vs. Sidekiq: Which Is Better?
https://github.com/mhenrixon/sidekiq-unique-jobs
All of which also extend the web UI for Sidekiq which is incredibly useful for both debugging and having a handle on what's with your queues.
Finally, if you're going to be using Sidekiq in any serious way I'd recommend Nate Berkopec's "Sidekiq in Practice" - https://nateberk.gumroad.com/l/sidekiqinpractice
Beyond being an incredibly useful resource on its own - you get access to a very active private Slack that is filled with other very helpful developers who are using Sidekiq.
-
Getting Sidekiq to play nicely with auto-scaling
That's an interesting suggestion. We're relying on ActiveJob and sidekiq-unique-jobs doesn't explicitly support it, unfortunately. We'll have to test it out, though, and see if it just happens to work.
What are some alternatives?
pg_search - pg_search builds ActiveRecord named scopes that take advantage of PostgreSQL’s full text search
sidekiq-throttled - Concurrency and rate-limit throttling for Sidekiq
pg_easy_replicate - Easily setup logical replication and switchover to new database with minimal downtime
job-iteration - Makes your background jobs interruptible and resumable by design.
Sidekiq-Cron - Scheduler / Cron for Sidekiq jobs
good_job - Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.
sidekiq - Sidekiq worker on Render
sidekiq-statistic - See statistic about your workers
sidekiq-scheduler - Lightweight job scheduler extension for Sidekiq
heroku-buildpack-jemalloc - Heroku buildpack that installs the Jemalloc memory allocator
sidekiq-failures - Keep track of Sidekiq failed jobs
inst-jobs - Instructure-maintained fork of delayed_job