Need advice about which tool to choose?Ask the StackShare community!
Kue vs Redis: What are the differences?
Kue: Kue is a priority job queue backed by redis, built for node.js. 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; Redis: An in-memory database that persists on disk. 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.
Kue belongs to "Background Processing" category of the tech stack, while Redis can be primarily classified under "In-Memory Databases".
Kue and Redis are both open source tools. Redis with 37.1K GitHub stars and 14.3K forks on GitHub appears to be more popular than Kue with 8.74K GitHub stars and 880 GitHub forks.
According to the StackShare community, Redis has a broader approval, being mentioned in 3239 company stacks & 1735 developers stacks; compared to Kue, which is listed in 6 company stacks and 4 developer stacks.
Pros of Kue
- Simple2
Pros of Redis
- Performance887
- Super fast542
- Ease of use514
- In-memory cache444
- Advanced key-value cache324
- Open source194
- Easy to deploy182
- Stable165
- Free156
- Fast121
- High-Performance42
- High Availability40
- Data Structures35
- Very Scalable32
- Replication24
- Pub/Sub23
- Great community22
- "NoSQL" key-value data store19
- Hashes16
- Sets13
- Sorted Sets11
- Lists10
- NoSQL10
- Async replication9
- BSD licensed9
- Integrates super easy with Sidekiq for Rails background8
- Bitmaps8
- Open Source7
- Keys with a limited time-to-live7
- Lua scripting6
- Strings6
- Awesomeness for Free5
- Hyperloglogs5
- Runs server side LUA4
- Transactions4
- Networked4
- Outstanding performance4
- Feature Rich4
- Written in ANSI C4
- LRU eviction of keys4
- Data structure server3
- Performance & ease of use3
- Temporarily kept on disk2
- Dont save data if no subscribers are found2
- Automatic failover2
- Easy to use2
- Scalable2
- Channels concept2
- Object [key/value] size each 500 MB2
- Existing Laravel Integration2
- Simple2
Sign up to add or upvote prosMake informed product decisions
Cons of Kue
Cons of Redis
- Cannot query objects directly15
- No secondary indexes for non-numeric data types3
- No WAL1
Sign up to add or upvote consMake informed product decisions
What is Kue?
What is Redis?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Kue?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kue?
What tools integrate with Redis?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+9
+8
+17
+9
+12+23+17