Software Alternatives, Accelerators & Startups

delayed_job VS NATS

Compare delayed_job VS NATS and see what are their differences

delayed_job logo delayed_job

Database based asynchronous priority queue system -- Extracted from Shopify - collectiveidea/delayed_job

NATS logo NATS

NATS.io is an open source messaging system for cloud native applications, IoT messaging, Edge, and microservices architectures.
  • delayed_job Landing page
    Landing page //
    2022-11-02
  • NATS Landing page
    Landing page //
    2023-01-05

NATS.io is a connective technology for distributed systems and is a perfect fit to connect devices, edge, cloud or hybrid deployments. True multi-tenancy makes NATS ideal for SaaS and self-healing and scaling technology allows for topology changes anytime with zero downtime.

delayed_job videos

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

+ Add video

NATS videos

The coolest OSS project you've never heard of: NATS Getting started!

Category Popularity

0-100% (relative to delayed_job and NATS)
Data Integration
28 28%
72% 72
Developer Tools
0 0%
100% 100
Stream Processing
100 100%
0% 0
Ruby On Rails
100 100%
0% 0

User comments

Share your experience with using delayed_job and NATS. 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 delayed_job and NATS

delayed_job Reviews

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

NATS Reviews

Best message queue for cloud-native apps
NATS is designed to be simple and easy to use, with a small footprint and low latency. It is often used in cloud-native environments to connect different components of a distributed system or to enable communication between microservices. NATS also supports message persistence, security, and clustering, making it a robust messaging system for building scalable and resilient...
Source: docs.vanus.ai
Are Free, Open-Source Message Queues Right For You?
One challenge of NATS is that it does not support reliable message queuing out of the box - messages can be lost if a client disconnects before it receives them. This can be mitigated by using NATS Streaming, a data streaming system powered by NATS, but it adds complexity.
Source: blog.iron.io
NATS vs RabbitMQ vs NSQ vs Kafka | Gcore
NATS is known for its high performance, low latency, and emphasis on simplicity after it was rewritten in Go. Its rewrite in Go makes NATS an ideal choice for demanding and real-time applications and has increased its throughput compared to its original Ruby implementation.
Source: gcore.com

Social recommendations and mentions

Based on our record, NATS seems to be a lot more popular than delayed_job. While we know about 65 links to NATS, we've tracked only 6 mentions of delayed_job. 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.

delayed_job mentions (6)

  • It’s Time For Active Job
    It is hard to imagine any big and complex Rails project without background jobs processing. There are many gems for this task: **Delayed Job, Sidekiq, Resque, SuckerPunch** and more. And Active Job has arrived here to rule them all. - Source: dev.to / 5 days ago
  • DelayedJob and PG Error No Connection to Server
    Obviously, that is not what I’ve expected from Delayed::Job workers. So I took the shovel and started digging into git history. Since the last release the only significant modification has been made in the internationalization. We’ve moved to I18n-active_record backend to grant the privilege to modify translations not only to developers but also to highly-educated mere mortals. - Source: dev.to / 5 days ago
  • 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 / over 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
View more

NATS mentions (65)

  • HN-text: an easy-to-use, text-first Hacker News terminal client
    That sounds awesome. I have actually been working on something similar myself. I have been building a distributed NATS[0] cluster to funnel data down from the internet and index it locally. I also have a local Ollama box wired up to try to do some NLP on it. I started with Benthos to pull in, but since the recent license changes[1] I am rethinking that :( If you would like to collaborate feel free to shoot me an... - Source: Hacker News / 10 days ago
  • Hello World, Simple Event Broker
    I've been happy with NATS, https://nats.io/. - Source: Hacker News / 14 days ago
  • Implementing OTel Trace Context Propagation Through Message Brokers with Go
    Several message brokers, such as NATS and database queues, are not supported by OpenTelemetry (OTel) SDKs. This article will guide you on how to use context propagation explicitly with these message queues. - Source: dev.to / 2 months ago
  • NATS: First Impressions
    Https://nats.io/ (Tracker removed) > Connective Technology for Adaptive Edge & Distributed Systems > An Introduction to NATS - The first screencast I guess I don't need to know what it is. - Source: Hacker News / 2 months ago
  • Sequential and parallel execution of long-running shell commands
    Pueue dumps the state of the queue to the disk as JSON every time the state changes, so when you have a lot of queued jobs this results in considerable disk io. I actually changed it to compress the state file via zstd which helped quite a bit but then eventually just moved on to running NATS [1] locally. [1] https://nats.io/. - Source: Hacker News / 3 months ago
View more

What are some alternatives?

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

Sidekiq - Sidekiq is a simple, efficient framework for background job processing in Ruby

Socket.io - Realtime application framework (Node.JS server)

Hangfire - An easy way to perform background processing in .NET and .NET Core applications.

Firebase - Firebase is a cloud service designed to power real-time, collaborative applications for mobile and web.

Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.

Pusher - Pusher is a hosted API for quickly, easily and securely adding scalable realtime functionality via WebSockets to web and mobile apps.