Software Alternatives & Reviews

NSQ VS delayed_job

Compare NSQ VS delayed_job and see what are their differences

NSQ logo NSQ

A realtime distributed messaging platform.

delayed_job logo delayed_job

Database based asynchronous priority queue system -- Extracted from Shopify - collectiveidea/delayed_job
  • NSQ Landing page
    Landing page //
    2023-07-07
  • delayed_job Landing page
    Landing page //
    2022-11-02

NSQ videos

GopherCon 2014 Spray Some NSQ On It by Matt Reiferson

More videos:

delayed_job videos

No delayed_job videos yet. You could help us improve this page by suggesting one.

+ Add video

Category Popularity

0-100% (relative to NSQ and delayed_job)
Stream Processing
65 65%
35% 35
Data Integration
61 61%
39% 39
Web Service Automation
100 100%
0% 0
Ruby On Rails
0 0%
100% 100

User comments

Share your experience with using NSQ and delayed_job. For example, how are they different and which one is better?
Log in or Post with

Reviews

These are some of the external sources and on-site user reviews we've used to compare NSQ and delayed_job

NSQ Reviews

NATS vs RabbitMQ vs NSQ vs Kafka | Gcore
NSQ is designed with a distributed architecture around the concept of topics, which allows messages to be organized and distributed across the cluster. To ensure reliable delivery, NSQ replicates each message across multiple nodes within the NSQ cluster. This means that if a node fails or there’s a disruption in the network, the message can still be delivered to its intended...
Source: gcore.com

delayed_job Reviews

We have no reviews of delayed_job yet.
Be the first one to post

Social recommendations and mentions

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.

NSQ mentions (7)

  • Any thoughts on using Redis to extend Go's channels across application / machine boundaries?
    (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
  • FileWave: Why we moved from ZeroMQ to NATS
    Bit.ly's NSQ is also an excellent message queue option. Source: about 1 year ago
  • Infinite loop pattern to poll for a queue in a REST server app
    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
  • What are pros and cons of Go?
    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
  • Distributed IM Service in Golang
    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
View more

delayed_job mentions (4)

  • How to run a really long task from a Rails web request
    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
  • Delayed Job vs. Sidekiq: Which Is Better?
    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
  • Why does rails have a tradition of queuing background jobs in a separate NoSQL store, when both the queueing controller and the job class tend to hammer the main database anyway?
    Back in the day, before Sidekiq and such, we used Delayed Job https://github.com/collectiveidea/delayed_job. Source: over 2 years ago
  • A quick look at background jobs in Ruby
    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

What are some alternatives?

When comparing NSQ and delayed_job, you can also consider the following products

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.