node package manager


Cache module for Node.js

build status Coverage Status


Flexible NodeJS cache module

A cache module for nodejs that allows easy wrapping of functions in cache, tiered caches, and a consistent interface.


  • Easy way to wrap any function in cache.
  • Tiered caches -- data gets stored in each cache and fetched from the highest priority cache(s) first.
  • Use any cache you want, as long as it has the same API.
  • 100% test coverage via mocha, istanbul, and sinon.

Express.js Example

See the Express.js cache-manager example app to see how to use node-cache-manager in your applications.


npm install cache-manager

Store Engines


First, it includes a wrap function that lets you wrap any function in cache. (Note, this was inspired by node-caching.) This is probably the feature you're looking for. As an example, where you might have to do this:

function getCachedUser(id, cb) {
    memoryCache.get(id, function (err, result) {
        if (err) { return cb(err); }
        if (result) {
            return cb(null, result);
        getUser(id, function (err, result) {
            if (err) { return cb(err); }
            memoryCache.set(id, result);
            cb(null, result);

... you can instead use the wrap function:

function getCachedUser(id, cb) {
    memoryCache.wrap(id, function (cacheCallback) {
        getUser(id, cacheCallback);
    }, {ttl: ttl}, cb);

Second, node-cache-manager features a built-in memory cache (using node-lru-cache), with the standard functions you'd expect in most caches:

set(key, val, {ttl: ttl}, cb) // * see note below
get(key, cb)
del(key, cb)

// * Note that depending on the underlying store, you may be able to pass the
// ttl as the third param, like this:
set(key, val, ttl, cb)
// ... or pass no ttl at all:
set(key, val, cb)

Third, node-cache-manager lets you set up a tiered cache strategy. This may be of limited use in most cases, but imagine a scenario where you expect tons of traffic, and don't want to hit your primary cache (like Redis) for every request. You decide to store the most commonly-requested data in an in-memory cache, perhaps with a very short timeout and/or a small data size limit. But you still want to store the data in Redis for backup, and for the requests that aren't as common as the ones you want to store in memory. This is something node-cache-manager handles easily and transparently.

Usage Examples

See examples below and in the examples directory. See examples/redis_example for an example of how to implement a Redis cache store with connection pooling.

Single Store

var cacheManager = require('cache-manager');
var memoryCache = cacheManager.caching({store: 'memory', max: 100, ttl: 10/*seconds*/});
var ttl = 5;
// Note: callback is optional in set() and del(). 
memoryCache.set('foo', 'bar', {ttl: ttl}, function(err) {
    if (err) { throw err; }
    memoryCache.get('foo', function(err, result) {
        // >> 'bar' 
        memoryCache.del('foo', function(err) {});
function getUser(id, cb) {
    setTimeout(function () {
        console.log("Returning user from slow database.");
        cb(null, {id: id, name: 'Bob'});
    }, 100);
var userId = 123;
var key = 'user_' + userId;
// Note: ttl is optional in wrap() 
memoryCache.wrap(key, function (cb) {
    getUser(userId, cb);
}, {ttl: ttl}, function (err, user) {
    // Second time fetches user from memoryCache 
    memoryCache.wrap(key, function (cb) {
        getUser(userId, cb);
    }, function (err, user) {
// Outputs: 
// Returning user from slow database. 
// { id: 123, name: 'Bob' } 
// { id: 123, name: 'Bob' } 

The ttl can also be computed dynamicall by passing in a function. E.g.,

var opts = {
    ttl: function(user) {
        if ( === 1) {
            return 0.1;
        } else {
            return 0.5;
memoryCache.wrap(key, function(cb) {
    getUser(userId, cb);
}, opts, function(err, user) {

Example Using Promises

memoryCache.wrap(key, function() {
    return getUserPromise(userId);
.then(function(user) {
    console.log('User:', user);

If you are using a Node version that does not include native promises, you can specify your promise dependency in the options passed to the cache module. E.g.,

var Promise = require('es6-promise').Promise;
cache = caching({store: store, promiseDependency: Promise});

Example Express App Usage

(Also see the Express.js cache-manager example app).

function respond(res, err, data) {
    if (err) {
        res.json(500, err);
    } else {
        res.json(200, data);
app.get('/foo/bar', function(req, res) {
    var cacheKey = 'foo-bar:' + JSON.stringify(req.query);
    var ttl = 10;
    memoryCache.wrap(cacheKey, function(cacheCallback) {
        DB.find(req.query, cacheCallback);
    }, {ttl: ttl}, function(err, result) {
        respond(res, err, result);

Custom Stores

You can use your own custom store by creating one with the same API as the built-in memory stores (such as a redis or memcached store). To use your own store just pass in an instance of it.


var myStore = require('your-homemade-store');
var cache = cacheManager.caching({store: myStore});


var multiCache = cacheManager.multiCaching([memoryCache, someOtherCache]);
userId2 = 456;
key2 = 'user_' + userId;
ttl = 5;
// Sets in all caches. 
multiCache.set('foo2', 'bar2', {ttl: ttl}, function(err) {
    if (err) { throw err; }
    // Fetches from highest priority cache that has the key. 
    multiCache.get('foo2', function(err, result) {
        // >> 'bar2' 
        // Delete from all caches 
// Note: options with ttl are optional in wrap() 
multiCache.wrap(key2, function (cb) {
    getUser(userId2, cb);
}, {ttl: ttl}, function (err, user) {
    // Second time fetches user from memoryCache, since it's highest priority. 
    // If the data expires in the memory cache, the next fetch would pull it from 
    // the 'someOtherCache', and set the data in memory again. 
    multiCache.wrap(key2, function (cb) {
        getUser(userId2, cb);
    }, function (err, user) {

Specifying What to Cache in wrap Function

Both the caching and multicaching modules allow you to pass in a callback function named isCacheableValue which is called by the wrap function with every value returned from cache or from the wrapped function. This lets you specify which values should and should not be cached by wrap. If the function returns true, it will be stored in cache. By default the caches cache everything except undefined.

NOTE: The set functions in caching and multicaching do not use isCacheableValue.

For example, if you don't want to cache false and null, you can pass in a function like this:

var isCacheableValue = function(value) {
    return value !== null && value !== false && value !== undefined;

Then pass it to caching like this:

var memoryCache = cacheManager.caching({store: 'memory', isCacheableValue: isCacheableValue});

And pass it to multicaching like this:

var multiCache = cacheManager.multiCaching([memoryCache, someOtherCache], {
    isCacheableValue: isCacheableValue


To generate JSDOC 3 documentation:

make docs


To run tests, first run:

npm install -d

Run the tests and JShint:



If you would like to contribute to the project, please fork it and send us a pull request. Please add tests for any new features or bug fixes. Also run make before submitting the pull request.


node-cache-manager is licensed under the MIT license.