job-iteration
activejob-uniqueness
| job-iteration | activejob-uniqueness | |
|---|---|---|
| 5 | 1 | |
| 1,025 | 250 | |
| 0.9% | 1.2% | |
| 8.6 | 4.7 | |
| 6 days ago | 4 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.
job-iteration
-
Gnarly Learnings from December 2022
Shopify/Job-Iteration
-
Announcing sidekiq-iteration - a gem that makes your sidekiq jobs interruptible and resumable by design
I am publishing a new gem - https://github.com/fatkodima/sidekiq-iteration. For those familiar with job-iteration (https://github.com/Shopify/job-iteration) from Shopify, this is an adoption of that gem to be used with raw Sidekiq (no ActiveJob).
-
Making background jobs more resilient by default
Now that we are batching data together, we want to limit how long a single job can run. In order to tackle this, we leveraged functionality from the job-iteration gem. This gem provides an interface where we can define an enumerator and what to do each iteration. The gem will handle the rest. Utilizing this, our job and module will now look like this: (For ease of reading, the bit of code already shown has been removed.)
-
Why does this function use a lot of memory?
For advanced use cases, check out https://github.com/Shopify/job-iteration which keeps track of progress and can resume after deployment/VM eviction/etc
-
Getting Sidekiq to play nicely with auto-scaling
If that's the case, https://github.com/Shopify/job-iteration could help by making all your jobs easily interruptible.
activejob-uniqueness
-
Making background jobs more resilient by default
Now that data is batched together and individual jobs are handling things in batches, we want to prevent race conditions of multiple jobs running at once. We solved this by using the activejob-uniqueness gem.
What are some alternatives?
Sidekiq - Simple, efficient background processing for Ruby
acidic_job - Idempotent operations for Rails apps, built for ActiveJob or Sidekiq.
sidekiq-unique-jobs - Prevents duplicate Sidekiq jobs
redlock-rb - Redlock is a redis-based distributed lock implementation in Ruby. More than 20M downloads.
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
crystal - The Crystal Programming Language
Shoryuken - A super efficient Amazon SQS thread based message processor for Ruby
sidekiq-iteration - Make your long-running sidekiq jobs interruptible and resumable.
good_job - Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.
Ruby on Rails - Ruby on Rails