npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

stow

v2.2.0

Published

Caching with a flexible invalidation strategy

Downloads

145

Readme

stow

Node.js caching with a flexible invalidation strategy.

build status

There are only two hard things in Computer Science: cache invalidation and naming things.

-- Phil Karlton

The oft-tweeted quote above, while mostly just a humorous anecdote, can often feel like reality. Stow aims to solve both problems with an easy-to-remember name and a caching API built around tag-based invalidation.

Usage

var stow = require('stow')
var RedisBackend = require('stow/backends/redis')
var redis = require('redis')

// Create your cache.
var cache = stow.createCache(RedisBackend, {
  client: redis.createClient()
})

// Add items to the cache.
cache.set('my:cache:key', 'my data', {'user': 47, 'comment': [4, 82, 199]}, function (err) {
  // Handle error
})

// Or use an options hash.
cache.set({
  key: 'my:cache:key',
  data: {my: 'data'},
  ttl: 3600 * 24, // TTL in seconds
  tags: {user: 52}
}, function (err) {
  // Handle error
})

// Retreive from the cache.
cache.get('my:cache:key', function (err, result) {
  // result.data contains your data.
  // result is `false` on a cache miss.
})

// Invalidate items based on one or more tag(s).
cache.invalidate({'user': 47}, function (err) {
  // Cached data 'tagged' with user 47 was invalidated.
})

// Clear items (using wildcard)
cache.clear('my:cache:*', function (err) {
  // Handle error
})

API

stow.createCache ( backend , [options] )

  • backend - The backend class to use.
  • options - Constructor options passed to the backend when it is created.
  • returns an instance of stow.Cache.
  var stow = require('stow')
  var MemoryBackend = require('stow/backends/memory')
  var cache = stow.createCache(MemoryBackend, {ttl: 3600})

stow.Cache (Class)

Class that exposes the public cache methods.

Instance Properties

cache.backend

Reference to the Backend instance for this cache.

Instance Methods

cache.set ( options , cb )

Add items to the cache.

  • options
    • key - A unique string identifying the cached item.
    • data - The data you wish to cache. Will be serialized via hydration.
    • ttl - Time until cache expires (in seconds). Defaults to 0 (unlimited).
    • tags - An Object containing the tags to associate with this cached item.
  • cb (err) - Called after the item has been cached.
cache.set ( key, data, [ttl], [tags], cb)

Add items to the cache (alternative syntax).

  • key - A unique string identifying the cached item.
  • data - The data you wish to cache. Will be serialized via hydration.
  • ttl - Time until cache expires (in seconds). Defaults to 0 (unlimited).
  • tags - An Object containing the tags to associate with this cached item.
  • cb (err) - Called after the item has been cached.
cache.get ( key, cb )

Retrieve items from the cache.

  • key - A unique string identifying the cached item.
  • cb (err, result) - Called when the item has been retrieved.
    • err - The retrieval error, if any.
    • result - The cached item along with cache metadata.
      • result.data - Your cached data, unserialized.
cache.invalidate ( tags, cb )

Invalidate cached items if they were tagged with ANY of the passed tags.

  • tags - An Object containing the tags to invalidate.
  • cb (err) - Called after the invalidation is complete.
cache.clear ( [key] , cb)

Clear items from the cache by key or wildcard key pattern.

  • key - A string identidying the item to clear, or a wildcard pattern that will clear multiple cached items. Examples: my:cache:key, users:*, *:formatted:*. WARNING: Depending on the backend used and the size of your cache, wildcard clears can be quite slow and expensive. Use with care.
  • cb (err) - Called after the clear is complete.

Backends

Backends are responsible for storage, retrieval and invalidation. Stow ships with a memory backend for testing and a Redis backend for production use. If you wish to create another backend please check out the Backend Spec.

Memory Backend

The memory backend stores the cache in your node process' local memory space. This backend is suitable for testing and development but has not been optimized for performance or long-term use.

var stow = require('stow')
var MemoryBackend = require('stow/backends/memory')
var options = {}
var cache = stow.createCache(MemoryBackend, options)

Options:

  • max - The maximum number of items to store in the cache. Helps prevent memory leaks. Defaults to 5000.
  • ttl - Default TTL (in seconds) to use for ALL cached items. Can be overriden per cache set. Defaults to 24 hours.

Mongo Backend

The Mongo backend stores cached items in MongoDB. It uses TTL support baked into Mongo and is otherwise optimized for production use.

var stow = require('stow')
var MongoBackend = require('stow/backends/mongo')
var MongoClient = require('mongodb').MongoClient
var options = {}

MongoClient.connect('mongodb://localhost:27017/my_db', function (err, db) {
  if (err) return done(err)
  options.db = db
  var cache = stow.createCache(RedisBackend, options);
})

Options:

  • db - The backend will use this mongodb-native database object.
  • ttl - Default TTL to use for ALL cached items. Can be overriden per cache set. Defaults to 0 (unlimited).
  • coll - A string used to name the cache and cache_tags collections. Default: 'stow'.

Redis Backend

The Redis backend stores cached items in Redis. It uses TTL support baked into Redis and is otherwise optimized for production use.

var stow = require('stow')
var RedisBackend = require('stow/backends/redis')
var redis = require('redis')
var options = {
  client: redis.createClient
}
var cache = stow.createCache(RedisBackend, options);

Options:

  • client - The backend will use this redis client.
  • ttl - Default TTL to use for ALL cached items. Can be overriden per cache set. Defaults to 0 (unlimited).
  • prefix - A string to prefix all redis keys with. Default: 'stow:'.

Credits

Stow is based on the excellent Drupal cache module: CacheTags. The invalidation strategy used in CacheTags has been in high-traffic production deployments with millions of objects for more than 2 years.


Developed by Terra Eclipse

Terra Eclipse, Inc. is a nationally recognized political technology and strategy firm located in Aptos, CA and Washington, D.C.


License: MIT

Copyright (C) 2016 Terra Eclipse, Inc. (http://www.terraeclipse.com)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.