Software Alternatives, Accelerators & Startups

Faye VS delayed_job

Compare Faye VS delayed_job and see what are their differences

Faye logo Faye

Simple pub/sub messaging for the web

delayed_job logo delayed_job

Database based asynchronous priority queue system -- Extracted from Shopify - collectiveidea/delayed_job
  • Faye Landing page
    Landing page //
    2021-10-17
  • delayed_job Landing page
    Landing page //
    2022-11-02

Faye videos

Chloé Faye: Review & What's In My Bag | The Anna Edit

More videos:

  • Review - CHLOE FAYE UPDATE/ REVIEW!
  • Review - ONE YEAR LATER | Chloe Faye Review | Preowned | Ana Maria

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 Faye and delayed_job)
Developer Tools
100 100%
0% 0
Data Integration
30 30%
70% 70
Mobile Push Messaging
100 100%
0% 0
Stream Processing
0 0%
100% 100

User comments

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

Social recommendations and mentions

Based on our record, delayed_job should be more popular than Faye. It has been mentiond 4 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.

Faye mentions (2)

  • 8 Best WebSocket Libraries For Node
    Faye WebSocket is a versatile WebSocket implementation derived from the Faye project. Faye is a messaging system that uses the Publish/Subscribe model and the Bayeux protocol. It provides message servers for Node, Ruby, and all major web browsers. - Source: dev.to / 7 months ago
  • Which self hosted Pub/Sub realtime technology (websockets etc) do you use and why?
    I can find socket.io, faye, deepstream.io , autobahn-js and nchan, centrifugo. Can you also explain why you chose it and if you had troubles with some other solution? Source: about 3 years ago

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 Faye and delayed_job, you can also consider the following products

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

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

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

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

NATS - NATS.io is an open source messaging system for cloud native applications, IoT messaging, Edge, and microservices architectures.

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