StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Caching
  4. Managed Memcache
  5. Kue vs Memcached Cloud

Kue vs Memcached Cloud

OverviewComparisonAlternatives

Overview

Memcached Cloud
Memcached Cloud
Stacks12
Followers16
Votes24
Kue
Kue
Stacks51
Followers88
Votes2
GitHub Stars9.5K
Forks871

Kue vs Memcached Cloud: What are the differences?

What is 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.

What is Memcached Cloud? A fully-managed service for hosting and running your memcached in a reliable and fail-safe manner. Memcached Cloud is a fully-managed service for running your Memcached in a reliable and fail-safe manner. Your dataset is constantly replicated, so if a node fails, an auto-switchover mechanism guarantees data is served without interruption. Memcached Cloud provides various data persistence options as well as remote backups for disaster recovery purposes.

Kue and Memcached Cloud are primarily classified as "Background Processing" and "Managed Memcache" tools respectively.

Kue is an open source tool with 8.77K GitHub stars and 885 GitHub forks. Here's a link to Kue's open source repository on GitHub.

Gigster, Fraeber Labs Pvt Ltd, and Greenkeeper are some of the popular companies that use Kue, whereas Memcached Cloud is used by Frederick, CoverWallet, and Codix.io. Kue has a broader approval, being mentioned in 6 company stacks & 5 developers stacks; compared to Memcached Cloud, which is listed in 3 company stacks and 4 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Memcached Cloud
Memcached Cloud
Kue
Kue

Memcached Cloud is a fully-managed service for running your Memcached in a reliable and fail-safe manner. Your dataset is constantly replicated, so if a node fails, an auto-switchover mechanism guarantees data is served without interruption. Memcached Cloud provides various data persistence options as well as remote backups for disaster recovery purposes.

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.

true high-availability;fast storage engine;backups and imports;infinite seamless scalability;predictable high-performance;multiple buckets in a plan;ssl authentication & encryption;email alerts;fully-automated service;24/7 monitoring & support
-
Statistics
GitHub Stars
-
GitHub Stars
9.5K
GitHub Forks
-
GitHub Forks
871
Stacks
12
Stacks
51
Followers
16
Followers
88
Votes
24
Votes
2
Pros & Cons
Pros
  • 6
    High-availability
  • 6
    Heroku add-on
  • 3
    Fast
  • 2
    Fail-safe
  • 2
    Email alerts
Pros
  • 2
    Simple
Integrations
Amazon S3
Amazon S3
Redis
Redis
Heroku
Heroku
Memcached
Memcached
No integrations available

What are some alternatives to Memcached Cloud, Kue?

Sidekiq

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.

Amazon ElastiCache

Amazon ElastiCache

ElastiCache improves the performance of web applications by allowing you to retrieve information from fast, managed, in-memory caches, instead of relying entirely on slower disk-based databases. ElastiCache supports Memcached and Redis.

Beanstalkd

Beanstalkd

Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.

MemCachier

MemCachier

MemCachier provides an easy and powerful managed caching solution for all your performance and scalability needs. It works with the ubiquitous memcache protocol so your favourite language and framework already supports it.

Hangfire

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

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.

delayed_job

delayed_job

Delayed_job (or DJ) encapsulates the common pattern of asynchronously executing longer tasks in the background. It is a direct extraction from Shopify where the job table is responsible for a multitude of core tasks.

Faktory

Faktory

Redis -> Sidekiq == Faktory -> Faktory. Faktory is a server daemon which provides a simple API to produce and consume background jobs. Jobs are a small JSON hash with a few mandatory keys.

Bull

Bull

The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity.

Flow-Like

Flow-Like

Mission-critical automation you can audit, control and run on-prem. No black boxes. No silent failures. No data leaks. Built for teams that cannot afford uncertainty.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase