pasupulaphani / node-redis-store

Simplistic node redis store ready can scale with generic-pool support

node-redis-store

Simplistic node redis store ready can scale with generic-pool support

Prerequisites

node >= 4 This module requires nodejs v4 or above as it has dependencies on es6 components such as Map, Set, Promise etc.

Getting started

    npm install node-redis-store

Usage

    const RedisStore = require("node-redis-store");
    const store = new RedisStore();

    // set
    store.set("key", {a: "b"});

API

• RedisStore([options])

options object properties

Name	Type	Description
name	string	Name your store
redisOptions	object	opts from node_redis#options-object-properties
poolOptions	object	opts from node-pool#createpool
logger	object	Inject your custom logger

Run tests

bash test.sh

Contribute

Discover how you can contribute by heading on over to the CONTRIBUTING.md file.

Backers

Maintainers

These amazing people are maintaining this project:

• Phani — view contributions

Sponsors

No sponsors yet! Will you be the first?

Contributors

These amazing people have contributed code to this project:

• Oliver Brooks

Discover how you can contribute by heading on over to the CONTRIBUTING.md file.

<script>(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');ga('create', 'UA-57413413-4', 'auto');ga('send', 'pageview');</script> ---

node-redis-store's Issues

Make redis-pool an event-emitter

extend generic-pool to be an event emitter.

acquire timeout

When pool is full, lib will block until a connection becomes available.

Is there a way to set a timeout on a connection attempt? I would rather not block indefinitely if the pool is full.

Get cache keys to use scan instead of retrieving all the keys

For large Redis databases, it can be a huge overhead while retrieving all the keys. Instead use scan on Redis

write load tests and publish performance metrics

What am I looking to achieve

Connection Pool Utilization

• Are the pools properly sized based on the expected load per runtime?
• Are pools constantly exhausted? Do we have a connection leak?

Connection Acquisition Time

• Are we perfectly configured and just need the amount of connections in the pool?
• Or do we see increasing Acquisition time (time it takes to get a connection from the pool) which tells us we need more connections to fulfill the demand.

ES7 async/await constructs

In order to use it with ES7 async/await constructs, it needs to be wrapped in ES6 Promises.

• Move to es7 and compile to others

Write API documentation

Use native Promise instead of Bluebird

handle invalid arguments for all functions and modules

Get cache key time left/expire time