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

remongo

v3.0.1

Published

Simple mongoose redis caching

Downloads

4

Readme

remongo

Build Status npm version Known Vulnerabilities

Installation

$ npm install remongo

Usage

Mongoose

const mongoose = require('mongoose');
const redis = require('redis');
const Remongo = require('remongo');

const client = redic.createClient({
    host: '127.0.0.1',
    port: 6379
})

// default settings
const cache = new Remongo({
    client: client,                     // redis client
    prefix: 'cache',                    // redis key prefix
    ttl: 60,                            // time to live in secs (60 minimum), but cache.set() accepts lower values
    clear: {
        strategy: 'scanUnlinkChunks',   // cache clear method strategies, see Strategies
        chunk: 100                      // cache clear method chunk size, used in scan* strategies
    }
})

cache.attach(mongoose);

Strategies

There are many strategies / ways to clear your cache depending on your env & needs

delAll * Will use KEYS and then delete all keys found at once using DEL

delSeries * Will use KEYS and delete each key using DEL one after another

unlinkAll * Will use KEYS and then delete all keys found at once using UNLINK

unlinkSeries * Will use KEYS and delete each key using UNLINK one after another

scanDelAll * Will use SCAN with COUNT chunk defined in options and delete all keys using DEL

scanDelChunks * Will use SCAN with COUNT chunk defined in options and delete each chunk of keys one after another using DEL

scanUnlinkAll * Will use SCAN with COUNT chunk defined in options and delete all keys using UNLINK

scanUnlinkChunks * Will use SCAN with COUNT chunk defined in options and delete each chunk of keys one after another using UNLINK

API


// set
cache.set(key, value, ttl = (this.ttl || 60), cb = noop);

// get 
cache.get(key, cb = noop);

// del
cache.del(key, cb = noop);

// unlink
cache.unlink(key, cb = noop);

// clear
cache.clear(cb = noop);

// attach to mongoose
cache.attach(mongoose);

/**
 * 
 * mongoose
 * 
 */

// basic example
model.find({name:'John'}).populate('data').lean().cache(60).exec(); // populate & lean are supported (in case of lean models are not hydrated!)

// set custom cache key
model.find({name:'John'}).populate('data').lean().cache(60).setCacheKey('oh-poor-john').exec();

// get key (in case of custom)
const query = model.find({name:'John'}).populate('data').lean();
const key = query.getCacheKey(withPrefix = false);

// forget a cache entry
model.find({name:'John'}).populate('data').lean().forget(key); // key is optional but needed in case of custom key used

// forget a cache entry and exec
model.find({name:'John'}).populate('data').lean().forget().exec() // before .exec() you can re-cache etc etc...

Aggregate is also supported and has the same methods as mongoose model. Keep in mind that your model cache keys will have the following format:

  • model: cache:${modelName}:sha1
  • aggregate: cache:aggregate:sha1

Notes

Versions prior to 2.0.0 are unstable when used with mongoose

  • Need more mocha tests
  • Need contributors / maintenairs

Credits

This library was inspired by the cachegoose project.

License

(The MIT License)

Copyright (c) 2019 Panagiotis Raditsas

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.