Need advice about which tool to choose?Ask the StackShare community!

Kue

33
79
+ 1
2
RabbitMQ

14.9K
12.9K
+ 1
518
Redis

43.5K
32.4K
+ 1
3.9K
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Kue
Pros of RabbitMQ
Pros of Redis
  • 2
    Simple
  • 229
    It's fast and it works with good metrics/monitoring
  • 79
    Ease of configuration
  • 58
    I like the admin interface
  • 50
    Easy to set-up and start with
  • 20
    Durable
  • 18
    Intuitive work through python
  • 18
    Standard protocols
  • 10
    Written primarily in Erlang
  • 8
    Simply superb
  • 6
    Completeness of messaging patterns
  • 3
    Scales to 1 million messages per second
  • 3
    Reliable
  • 2
    Better than most traditional queue based message broker
  • 2
    Distributed
  • 2
    Supports AMQP
  • 1
    Inubit Integration
  • 1
    Supports MQTT
  • 1
    Runs on Open Telecom Platform
  • 1
    High performance
  • 1
    Reliability
  • 1
    Clusterable
  • 1
    Clear documentation with different scripting language
  • 1
    Great ui
  • 1
    Better routing system
  • 1
    Delayed messages
  • 875
    Performance
  • 535
    Super fast
  • 511
    Ease of use
  • 441
    In-memory cache
  • 321
    Advanced key-value cache
  • 190
    Open source
  • 179
    Easy to deploy
  • 163
    Stable
  • 153
    Free
  • 120
    Fast
  • 40
    High-Performance
  • 39
    High Availability
  • 34
    Data Structures
  • 32
    Very Scalable
  • 23
    Replication
  • 20
    Great community
  • 19
    Pub/Sub
  • 17
    "NoSQL" key-value data store
  • 14
    Hashes
  • 12
    Sets
  • 10
    Sorted Sets
  • 9
    Lists
  • 8
    BSD licensed
  • 8
    NoSQL
  • 7
    Async replication
  • 7
    Integrates super easy with Sidekiq for Rails background
  • 7
    Bitmaps
  • 6
    Open Source
  • 6
    Keys with a limited time-to-live
  • 5
    Strings
  • 5
    Lua scripting
  • 4
    Awesomeness for Free!
  • 4
    Hyperloglogs
  • 3
    outstanding performance
  • 3
    Runs server side LUA
  • 3
    Networked
  • 3
    LRU eviction of keys
  • 3
    Written in ANSI C
  • 3
    Feature Rich
  • 3
    Transactions
  • 2
    Data structure server
  • 2
    Performance & ease of use
  • 1
    Existing Laravel Integration
  • 1
    Automatic failover
  • 1
    Easy to use
  • 1
    Object [key/value] size each 500 MB
  • 1
    Simple
  • 1
    Channels concept
  • 1
    Scalable
  • 1
    Temporarily kept on disk
  • 1
    Dont save data if no subscribers are found
  • 0
    Jk

Sign up to add or upvote prosMake informed product decisions

Cons of Kue
Cons of RabbitMQ
Cons of Redis
    Be the first to leave a con
    • 9
      Too complicated cluster/HA config and management
    • 6
      Needs Erlang runtime. Need ops good with Erlang runtime
    • 5
      Configuration must be done first, not by your code
    • 4
      Slow
    • 14
      Cannot query objects directly
    • 2
      No secondary indexes for non-numeric data types
    • 1
      No WAL

    Sign up to add or upvote consMake informed product decisions

    What is Kue?

    Kue is a feature rich priority job queue for node.js backed by redis. A key feature of Kue is its clean user-interface for viewing and managing queued, active, failed, and completed jobs.

    What is RabbitMQ?

    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

    What is Redis?

    Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Kue?
    What companies use RabbitMQ?
    What companies use Redis?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Kue?
    What tools integrate with RabbitMQ?
    What tools integrate with Redis?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      Nov 20 2019 at 3:38AM

      OneSignal

      PostgreSQLRedisRuby+8
      8
      3933
      Jun 6 2019 at 5:11PM

      AppSignal

      RedisRubyKafka+9
      15
      1154
      GitHubDockerReact+17
      34
      30452
      What are some alternatives to Kue, RabbitMQ, and Redis?
      Bull
      The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity.
      Celery
      Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
      Sidekiq
      Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.
      Hangfire
      It is an open-source framework that helps you to create, process and manage your background jobs, i.e. operations you don't want to put in your request processing pipeline. It supports all kind of background tasks – short-running and long-running, CPU intensive and I/O intensive, one shot and recurrent.
      Resque
      Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.
      See all alternatives