Bee-Queue
Sidekiq
Bee-Queue | Sidekiq | |
---|---|---|
6 | 91 | |
3,625 | 12,950 | |
1.2% | 0.3% | |
8.5 | 8.9 | |
6 days ago | 6 days ago | |
JavaScript | Ruby | |
GNU General Public License v3.0 or later | 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.
Bee-Queue
-
Node.js backend architecture question
You could use a Redis based job system like https://github.com/bee-queue/bee-queue for maintenance and email. The jobs could be populated by the API service, some cron scripts, and whatever else, while you'd have dedicated worker processes (written in Node.js?) pulling the jobs and running them.
-
Building a task queue, Part 1
The Node.js libraries BullMQ and Bee Queue are also infrastructure and interface. However, you typically have to use their interface.
-
Scaling synchronous microservices
I'm a fan of bee-queue for this when working in Node, but it's just a wrapper around reliable queue patterns in Redis; you might want to investigate how it works (the readme is quite good) for your own use case, or find an equivalent for your environment. The key is it's designed for short tasks (seconds long, not minutes or hours), and you can receive a result back from the task unlike some fire-and-forget queueing solutions.
-
[Question] API routes and worker_threads
I'd also consider something like bee-queue, which would enable you to scale across processes or even across multiple server machines.
-
NodeJS recommended job queue/message queue??
For NodeJS, there are BullMQ(successor of Bull), Bull and Bee Queue
-
[AskJS] How do you do JS on the backend?
bee-queue for offloading tasks onto non-web-server machines
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?
bull - Premium Queue package for handling distributed jobs and messages in NodeJS.
Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.
kue - Kue is a priority job queue backed by redis, built for node.js.
Sneakers - A fast background processing framework for Ruby and RabbitMQ
Qedis
Shoryuken - A super efficient Amazon SQS thread based message processor for Ruby
The gist - BullMQ - Message Queue and Batch processing for NodeJS and Python based on Redis
Sucker Punch - Sucker Punch is a Ruby asynchronous processing library using concurrent-ruby, heavily influenced by Sidekiq and girl_friday.
node-resque - Node.js Background jobs backed by redis.
Apache Kafka - Mirror of Apache Kafka
piscina - A fast, efficient Node.js Worker Thread Pool implementation
celery - Distributed Task Queue (development branch)