No delayed_job videos yet. You could help us improve this page by suggesting one.
Based on our record, NSQ should be more popular than delayed_job. It has been mentiond 7 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
(G)NATS can do millions of messages per second and is the right tool for the job (either that or NSQ). Redis isn't even the fastest Redis protocol implementation, KeyDB significantly outperforms it. Source: about 1 year ago
Bit.ly's NSQ is also an excellent message queue option. Source: about 1 year ago
Queue consumers are interesting because there are many solutions for them, from using Redis and persisting the data in a data store - but for fast and scalable the approach I would take is something like SQS (as I advocate AWS even free tier) or NSQ for managing your own distributed producers and consumers. Source: over 1 year ago
Distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on). Source: almost 2 years ago
NSQ is a message queue implemented by Golang, and all messages are routed through NSQ. Reasons for choosing NSQ compared to other MQs: decentralized distribution (direct connection between production and consumption), low latency, No ordering, high performance, simple binary protocol. - Source: dev.to / about 2 years ago
So how do we trigger such a long-running process from a Rails request? The first option that comes to mind is a background job run by some of the queuing back-ends such as Sidekiq, Resque or DelayedJob, possibly governed by ActiveJob. While this would surely work, the problem with all these solutions is that they usually have a limited number of workers available on the server and we didn’t want to potentially... - Source: dev.to / about 2 years ago
Several gems support job queues and background processing in the Rails world — Delayed Job and Sidekiq being the two most popular ones. - Source: dev.to / about 2 years ago
Back in the day, before Sidekiq and such, we used Delayed Job https://github.com/collectiveidea/delayed_job. Source: over 2 years ago
There are a few of popular systems. A few need a database, such as Delayed::Job, while others prefer Redis, such as Resque and Sidekiq. - Source: dev.to / about 3 years ago
ZeroMQ - ZeroMQ is a high-performance asynchronous messaging library.
Sidekiq - Sidekiq is a simple, efficient framework for background job processing in Ruby
RabbitMQ - RabbitMQ is an open source message broker software.
Hangfire - An easy way to perform background processing in .NET and .NET Core applications.
nanomsg - nanomsg is a socket library that provides several common communication patterns.
Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.