Gathering detailed insights and metrics for redis-dataloader
Gathering detailed insights and metrics for redis-dataloader
Gathering detailed insights and metrics for redis-dataloader
Gathering detailed insights and metrics for redis-dataloader
npm install redis-dataloader
83.1
Supply Chain
99.5
Quality
77.7
Maintenance
100
Vulnerability
99.1
License
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
89 Stars
38 Commits
20 Forks
7 Watching
2 Branches
4 Contributors
Updated on 06 Mar 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
4.6%
1,083
Compared to previous day
Last week
9.1%
6,476
Compared to previous week
Last month
-0.4%
29,423
Compared to previous month
Last year
39.1%
298,499
Compared to previous year
3
6
Batching and Caching layer using Redis as the Caching layer. Redis Dataloader wraps Facebook Dataloader, adding Redis as a caching layer.
npm install redis-dataloader
or
yarn add redis-dataloader
1const redisClient = require('redis').createClient(); 2// the "ioredis" module is also supported 3// const Redis = require('ioredis'); 4// const redisClient = new Redis(); 5const DataLoader = require('dataloader'); 6const RedisDataLoader = require('redis-dataloader')({ redis: redisClient }); 7 8const loader = new RedisDataLoader( 9 // set a prefix for the keys stored in redis. This way you can avoid key 10 // collisions for different data-sets in your redis instance. 11 'redis-key-prefix', 12 // create a regular dataloader. This should always be set with caching disabled. 13 new DataLoader(myBatchLoadFunction, { cache: false }), 14 // The options here are the same as the regular dataloader options, with 15 // the additional option "expire" 16 { 17 // caching here is a local in memory cache. Caching is always done 18 // to redis. 19 cache: true, 20 // if set redis keys will be set to expire after this many seconds 21 // this may be useful as a fallback for a redis cache. 22 expire: 60, 23 // can include a custom serialization and deserialization for 24 // storage in redis. 25 serialize: date => date.getTime(), 26 deserialize: timestamp => new Date(timestamp), 27 // Set this to true to return Buffer objects to the deserialize function 28 // when using the ioredis driver. 29 buffer: false 30 } 31); 32 33// load an individual item by its key 34loader.load(5).then(resp => console.log(resp)); 35 36//clear an individiaul item from the local and redis cache. 37loader.clear(5).then(() => {})
In general, RedisDataLoader has the same API as the Facebook Dataloader Api, with a few differences. Read through the Facebook Dataloader documentation and then note the differences mentioned here.
clear
returns a promise (waits until redis succeeds at deleting the key). Facebook Dataloader's clear
method is synchronous.clearAll
is not available (redis does not have an efficient way to do this?)prime
will always overwrite the cache. Facebook Dataloader will only write to
its cache if a value is not already present. Prime is asyncronous and returns a Promise.null
or a JSON object.clearLocal(key)
and clearAllLocal()
allow you to clear the local cache only.1const redis = require('redis').createClient(); 2const RedisDataLoader = require('redis-dataloader')({ redis: redis });
Each Dataloader holds its own local in memory cache (Same as Facebook Dataloader), and additionally caches to your Redis instance.
1const loader = new RedisDataLoader('<redis key prefix>', '<Facebook Dataloader>', '<Options>');
Specify a Prefix that will be appended to each key when storing in Redis.
So for example if your prefix is "bar" and you call loader.load('foo')
, this key
will be stored in Redis as bar:foo
A regular Facebook Dataloader is passed in as the second parameter. It will be used to fetch data from your underlying datastore (mongo, sql, whatever). It is very important to disable the cache on this dataloader. Redis dataloader will already do local in memory caching (unless you disable it).
All the options available to Facebook Dataloader can be passed in here. An additional option called expire is also available, and will set a ttl in seconds on all keys set in redis if this option is passed.
The cacheKeyFn
will default to serialize objects and arrays using json-stable-stringify and allow all other values to pass through unchanged.
buffer
will pass a Buffer object to the deserialize function rather than a string.
If not using the ioredis driver this will throw an error at instation.
The purpose of Redis Dataloader is to provide a caching layer in redis on top of the Facebook Dataloader. Facebook's Dataloader provides a local in memory cache. This may be ok for short lived per-request caches, but may not be sufficient if you need a long lived cache and/or you have multiple webservers that need to share data.
Redis Dataloader will additionally use the same local cache that Facebook Dataloader provides. It will first check the local cache, then check the redis cache, before finally checking your underlying datastore. This pattern may be desirable if for example you create a new DataLoader for each request. If your dataloader is long-lived you may want to disable to the local cache, and just rely on the redis cache instead
1const loader = new RedisDataLoader('prefix', new DataLoader(), { cache: false });
npm install
docker-compose stop && docker-compose rm && docker-compose build && docker-compose up -d
npm test
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
4 existing vulnerabilities detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
Reason
Found 4/23 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More