cloudtasker
Sidekiq
cloudtasker | Sidekiq | |
---|---|---|
6 | 91 | |
147 | 12,950 | |
0.7% | 0.3% | |
8.0 | 8.9 | |
12 days ago | 6 days ago | |
Ruby | Ruby | |
MIT License | GNU Lesser General Public License v3.0 only |
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.
cloudtasker
-
Cloudtasker - Monitor your Cloud Tasks jobs on GCP
The Cloudtasker gem automatically adds a duration field on each "Job done" log entry. This value can be used to create a metric on job duration.
-
Google Cloud Tasks with Active Job
TL;DR; It is now possible to use Google Cloud Tasks with Active Job using the cloudtasker gem with the release of v0.11.0. If you intend to deploy your Rails app on Cloud Run, Cloudtasker is the easiest solution to get started with background jobs on Rails.
-
Google Cloud Tasks with Rails Active Job
We just released support for Active Job on cloudtasker, a gem for background jobs using Google Cloud Tasks as a backend.
-
Leveraging and expiring your cache for model, association and query caching in Rails
Let's take a concrete example: background jobs. Should you use ActiveJob, Sidekiq, Resque or Cloudtasker for GCP, it's very common to have jobs defined like this:
-
Background jobs for Rails on GCP using Cloud Tasks
Here is the link to the library: https://github.com/keypup-io/cloudtasker
-
Guide to deploying production Rails applications to GCP
Migrating from Sidekiq to Cloud Tasks using our cloudtasker gem is fairly easy considering they're pretty much using the same syntax. Don't hesitate to ask questions on the cloudtasker project if you need help!
Sidekiq
-
solid_queue alternatives - Sidekiq and good_job
3 projects | 21 Apr 2024
I'd say Sidekiq is the top competitor here.
-
Valkey Is Rapidly Overtaking Redis
There's something wrong at Redislabs, it took them over a year to get RESP3 rolled out into their hosted service, you'd expect a rollout of that to be a bit quicker when they're the owner of Redis.
It affected us when upgrading Sidekiq to version 7, which dropped support for older Redis, and their Envoy proxy setup didn't support HELLO and RESP3: https://github.com/sidekiq/sidekiq/issues/5594
-
Redis Re-Implemented with SQLite
That depends on how the `maxmemory-policy` is configured, and queue systems based on Redis will tell you not to allow eviction. https://github.com/sidekiq/sidekiq/wiki/Using-Redis#memory (it even logs a warnings if it detects your Redis is misconfigured IIRC).
-
3 one-person million dollar online businesses
Sidekiq https://sidekiq.org/: This one started as an open source project, once it got enough traction, the developer made a premium version of it, and makes money by selling licenses to businesses.
-
Choose Postgres Queue Technology
Sidekiq will drop in-progress jobs when a worker crashes. Sidekiq Pro can recover those jobs but with a large delay. Sidekiq is excellent overall but itβs not suitable for processing critical jobs with a low latency guarantee.
https://github.com/sidekiq/sidekiq/wiki/Reliability
-
We built the fastest CI in the world. It failed
> I'm not sure feature withholding has traditionally worked out well in the developer space.
I think it's worked out well for Sidekiq (https://sidekiq.org). I really like their model of layering valuable features between the OSS / Pro / Enterprise licenses.
-
Exploring concurrent rate limiters, mutexes, semaphores
I was studying Sidekiq's page on rate limiters. The first type of rate limiting mentioned is the concurrent limiter: only n tasks are allowed to run at any point in time. Note that this is independent of time units (e.g. per second), or how long they take to run. The only limitation is the number of concurrent tasks/requests.
- Ask HN: What are some of the most elegant codebases in your favorite language?
- Sidekiq and managing resumable jobs?
-
Organize Business Logic in Your Ruby on Rails Application
The code above isn't idempotent. If you run it twice, it will create two copies, which is probably not what you intended. Why is this important? Because most backend job processors like Sidekiq don't make any guarantees that your jobs will run exactly once.
What are some alternatives?
Sidekiq-Cron - Scheduler / Cron for Sidekiq jobs
Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
lambda_punch - ππ Asynchronous background job processing for AWS Lambda with Ruby using Lambda Extensions. Inspired by the SuckerPunch gem but specifically tooled to work with Lambda's invoke model.
Sneakers - A fast background processing framework for Ruby and RabbitMQ
Lowkiq - Ordered background jobs processing
Shoryuken - A super efficient Amazon SQS thread based message processor for Ruby
lambdakiq - ππ· ActiveJob with SQS & Lambda
Sucker Punch - Sucker Punch is a Ruby asynchronous processing library using concurrent-ruby, heavily influenced by Sidekiq and girl_friday.
cloudenvoy - Cross-application messaging for Ruby and Rails using Google Cloud Pub/Sub
Apache Kafka - Mirror of Apache Kafka
celery - Distributed Task Queue (development branch)
good_job - Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.