cacheman
Small and efficient cache provider for Node.JS with In-memory, File, Redis and MongoDB engines.
Installation
$ npm install cacheman
Usage
var Cacheman = ;var cache = ; // orvar cache = 'todo'; // orvar cache = ttl: 90 ; // orvar cache = 'todo' ttl: 90 ; // set the valuecache;
API
Cacheman([name, [options]])
Create cacheman
instance. It accepts an name
(optional) and options
(optional). options
can contain ttl
to set the default "Time To Live" in seconds, delimiter
to change the delimiter used for array keys (default: ':'
), Promise
can set a Promise library to use for promises, engine
that could be "memory", "in file", "redis" or "mongo", and the corresponding engine options that can be passed like port
, host
, etc.
You can also pass an already initialized client engine
as valid engine so you can re-use among multiple cacheman instances.
By default cacheman
uses the cacheman-memory
engine.
var options = ttl: 90 engine: 'redis' port: 9999 host: '127.0.0.1'; var cache = 'todo' options;
Reuse engine in multiple cache instances:
var Cacheman = ;var EngineMongo = ;var engine = ; // Share same engine:var todoCache = 'todo' engine: engine ;var blogCache = 'blog' engine: engine ;
cache.set(key, value, [ttl, [fn]])
Stores or updates a value.
cache; cache ;
Or add a TTL(Time To Live) in seconds like this:
// key will expire in 60 secondscache;
You can also use humman readable values for ttl
like: 1s
, 1m
, etc. Check out the ms project for additional information on supported formats.
// key will expire in 45 secondscache;
The key may also be an array. It will be joined into a string using the delimiter
option.
// equivalent to setting 'foo:bar'cache;
cache.get(key, fn)
Retrieves a value for a given key, if there is no value for the given key a null value will be returned.
cache; cache ;
cache.del(key, [fn])
Deletes a key out of the cache.
cache; cache ;
cache.clear([fn])
Clear the cache entirely, throwing away all values.
cacheclear { if err throw err; // cache is now clear}; cacheclear ;
cache.cache(key, data, ttl, [fn])
Cache shortcut method that support middleware. This method will first call get
and if the key is not found in cache it will call set
to save the value in cache.
cache; cache ;
cache.use(fn)
This method allow to add middlewares that will be executed when the cache
method
is called, meaning that you can intercept the function right after the get
and set
methods.
For example we can add a middleware that will force ttl of 10 seconds on all values to cache:
{ return { ; }}; cache; cache;
Or we can add a middleware to overwrite the value:
{ return { ; }}; cache; cache;
You can also pass errors as first argument to stop the cache execution:
{ return { ; }}; cache; cache;
cache.wrap(key, work, [ttl, [fn]])
Wraps a function in cache. The first time the function is run, its results are stored in cache so subsequent calls retrieve from cache instead of calling the function.
The work
function can call a node style callback argument or return a value including a promise.
The work
function and ttl
can also be passed in the opposite order. This is primarily to make promise returning calls cleaner.
{ ;} cache; cache ; cache ; cache ;
Run tests
$ make test
Supported engines
Credits
This library was inspired by the hilmi project.
License
(The MIT License)
Copyright (c) 2013 Jonathan Brumley <cayasso@gmail.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.