Security News
RubyGems.org Adds New Maintainer Role
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
petty-cache
Advanced tools
A cache module for node.js that uses a two-level cache (in-memory cache for recently accessed data plus Redis for distributed caching) with some extra features to avoid cache stampedes and thundering herds.
A cache module for Node.js that uses a two-level cache (in-memory cache for recently accessed data plus Redis for distributed caching) with automatic serialization plus some extra features to avoid cache stampedes and thundering herds.
Also includes mutex and semaphore distributed locking primitives.
Two-level cache Data is cached for 2 to 5 seconds in memory to reduce the amount of calls to Redis.
Jitter By default, cache values expire from Redis at a random time between 30 and 60 seconds. This helps to prevent a large amount of keys from expiring at the same time in order to avoid thundering herds (http://en.wikipedia.org/wiki/Thundering_herd_problem).
Double-checked locking Functions executed on cache misses are wrapped in double-checked locking (http://en.wikipedia.org/wiki/Double-checked_locking). This ensures the function called on cache miss will only be executed once in order to prevent cache stampedes (http://en.wikipedia.org/wiki/Cache_stampede).
Mutex Provides a distributed lock (mutex) with the ability to retry a specified number of times after a specified interval of time when acquiring a lock.
Semaphore Provides a pool of distributed locks with the ability to release a slot back to the pool or remove the slot from the pool so that it's not used again.
// Setup petty-cache
var PettyCache = require('petty-cache');
var pettyCache = new PettyCache();
// Fetch some data
pettyCache.fetch('key', function(callback) {
// This function is called on a cache miss
fs.readFile('file.txt', callback);
}, function(err, value) {
// This callback is called once petty-cache has loaded data from cache or executed the specified cache miss function
console.log(value);
});
Creates a new petty-cache client. port
, host
, and options
are passed directly to redis.createClient().
Attempts to retrieve the values of the keys specified in the keys
array. Any keys that aren't found are passed to cacheMissFunction as an array along with a callback that takes an error and an object, expecting the keys of the object to be the keys passed to cacheMissFunction
and the values to be the values that should be stored in cache for the corresponding key. Either way, the resulting error or key-value hash of all requested keys is passed to callback
.
Example
// Let's assume a and b are already cached as 1 and 2
pettyCache.bulkFetch(['a', 'b', 'c', 'd'], function(keys, callback) {
var results = {};
keys.forEach(function(key) {
results[key] = key.toUpperCase();
}
}, function(err, values) {
console.log(values); // {a: 1, b: 2, c: 'C', d: 'D'}
});
Options
{
ttl: 30000 // How long it should take for the cache entry to expire in milliseconds. Defaults to a random value between 30000 and 60000 (for jitter).
}
{
// TTL can optional be specified with a range to pick a random value between `min` and `max` (for jitter).
ttl: {
min: 5000,
max: 10000
}
}
Attempts to retrieve the values of the keys specified in the keys
array. Returns a key-value hash of all specified keys with either the corresponding values from cache or undefined
if a key was not found.
Example
pettyCache.get(['key1', 'key2', 'key3'], function(err, values) {
console.log(values);
});
Unconditionally sets the values for the specified keys.
Example
pettyCache.set({ key1: 'one', key2: 2, key3: 'three' }, function(err) {
if (err) {
// Handle error
}
});
Options
{
ttl: 30000 // How long it should take for the cache entries to expire in milliseconds. Defaults to a random value between 30000 and 60000 (for jitter).
}
{
// TTL can optional be specified with a range to pick a random value between `min` and `max` (for jitter).
ttl: {
min: 5000,
max: 10000
}
}
Attempts to retrieve the value from cache at the specified key. If it doesn't exist, it executes the specified cacheMissFunction that takes two parameters: an error and a value. cacheMissFunction
should retrieve the expected value for the key from another source and pass it to the given callback. Either way, the resulting error or value is passed to callback
.
Example
pettyCache.fetch('key', function(callback) {
// This function is called on a cache miss
fs.readFile('file.txt', callback);
}, function(err, value) {
// This callback is called once petty-cache has loaded data from cache or executed the specified cache miss function
console.log(value);
});
Options
{
ttl: 30000 // How long it should take for the cache entry to expire in milliseconds. Defaults to a random value between 30000 and 60000 (for jitter).
}
{
// TTL can optional be specified with a range to pick a random value between `min` and `max` (for jitter).
ttl: {
min: 5000,
max: 10000
}
}
Similar to pettyCache.fetch
but this method continually refreshes the data in cache by executing the specified cacheMissFunction before the TTL expires.
Example
pettyCache.fetchAndRefresh('key', function(callback) {
// This function is called on a cache miss and every TTL/2 milliseconds
fs.readFile('file.txt', callback);
}, function(err, value) {
console.log(value);
});
Options
{
ttl: 30000 // How long it should take for the cache entry to expire in milliseconds. Defaults to a random value between 30000 and 60000 (for jitter).
}
{
// TTL can optional be specified with a range to pick a random value between `min` and `max` (for jitter).
ttl: {
min: 5000,
max: 10000
}
}
Attempts to retrieve the value from cache at the specified key. Returns null
if the key doesn't exist.
Example
pettyCache.get('key', function(err, value) {
// `value` contains the value of the key if it was found in the in-memory cache or Redis. `value` is `null` if the key was not found.
console.log(value);
});
Updates an object at the given key with the property values provided. Sends an error to the callback if the key does not exist.
Example
pettyCache.patch('key', { a: 1 }, function(callback) {
if (err) {
// Handle redis or key not found error
}
// The object stored at 'key' now has a property 'a' with the value 1. Its other values are intact.
});
Options
{
ttl: 30000 // How long it should take for the cache entry to expire in milliseconds. Defaults to a random value between 30000 and 60000 (for jitter).
}
{
// TTL can optional be specified with a range to pick a random value between `min` and `max` (for jitter).
ttl: {
min: 5000,
max: 10000
}
}
Unconditionally sets a value for a given key.
Example
pettyCache.set('key', { a: 'b' }, function(err) {
if (err) {
// Handle redis error
}
});
Options
{
ttl: 30000 // How long it should take for the cache entry to expire in milliseconds. Defaults to a random value between 30000 and 60000 (for jitter).
}
{
// TTL can optional be specified with a range to pick a random value between `min` and `max` (for jitter).
ttl: {
min: 5000,
max: 10000
}
}
Attempts to acquire a distributed lock for the specified key. Optionally retries a specified number of times by waiting a specified amount of time between attempts.
pettyCache.mutex.lock('key', { retry: { interval: 100, times: 5 }, ttl: 1000 }, function(err) {
if (err) {
// We weren't able to acquire the lock (even after trying 5 times every 100 milliseconds).
}
// We were able to acquire the lock. Do work and then unlock.
pettyCache.mutex.unlock('key');
});
Options
{
retry: {
interval: 100, // The time in milliseconds between attempts to acquire the lock.
times: 1 // The number of attempts to acquire the lock.
},
ttl: 1000 // The maximum amount of time to keep the lock locked before automatically being unlocked.
}
Releases the distributed lock for the specified key.
pettyCache.mutex.unlock('key', function(err) {
if (err) {
// We weren't able to reach Redis. Your lock will expire after its TTL, but you might want to log this error.
}
});
Provides a pool of distributed locks. Once a consumer acquires a lock they have the ability to release the lock back to the pool or mark the lock as "consumed" so that it's not used again.
Example
// Create a new semaphore
pettyCache.semaphore.retrieveOrCreate('key', { size: 10 }, function(err) {
if (err) {
// Aw, snap! We couldn't create the semaphore
}
// Acquire a lock from the semaphore's pool
pettyCache.semaphore.acquireLock('key', { retry: { interval: 100, times: 5 }, ttl: 1000 }, function(err, index) {
if (err) {
// We couldn't acquire a lock from the semaphore's pool (even after trying 5 times every 100 milliseconds).
}
// We were able to acquire a lock from the semaphore's pool. Do work and then release the lock.
pettyCache.semaphore.releaseLock('key', index, function(err) {
if (err) {
// We weren't able to reach Redis. Your lock will expire after its TTL, but you might want to log this error.
}
});
// Or, rather than releasing the lock back to the semaphore's pool you can mark the lock as "consumed" to prevent it from being used again.
pettyCache.semaphore.consumeLock('key', index, function(err) {
if (err) {
// We weren't able to reach Redis. Your lock will expire after its TTL, but you might want to log this error.
}
});
});
});
Attempts to acquire a lock from the semaphore's pool. Optionally retries a specified number of times by waiting a specified amount of time between attempts.
// Acquire a lock from the semaphore's pool
pettyCache.semaphore.acquireLock('key', { retry: { interval: 100, times: 5 }, ttl: 1000 }, function(err, index) {
if (err) {
// We couldn't acquire a lock from the semaphore's pool (even after trying 5 times every 100 milliseconds).
}
// We were able to acquire a lock from the semaphore's pool. Do work and then release the lock.
});
Options
{
retry: {
interval: 100, // The time in milliseconds between attempts to acquire the lock.
times: 1 // The number of attempts to acquire the lock.
},
ttl: 1000 // The maximum amount of time to keep the lock locked before automatically being unlocked.
}
Mark the lock at the specified index as "consumed" to prevent it from being used again.
pettyCache.semaphore.consumeLock('key', index, function(err) {
if (err) {
// We weren't able to reach Redis. Your lock will expire after its TTL, but you might want to log this error.
}
});
Expand the number of locks in the specified semaphore's pool.
pettyCache.semaphore.expand(key, 100, function(err) {
if (err) {
// We weren't able to expand the semaphore.
}
});
Releases the lock at the specified index back to the semaphore's pool so that it can be used again.
pettyCache.semaphore.releaseLock('key', index, function(err) {
if (err) {
// We weren't able to reach Redis. Your lock will expire after its TTL, but you might want to log this error.
}
});
Resets the semaphore to its initial state effectively releasing all locks (even those that have been marked as "consumed").
pettyCache.semaphore.reset('key', function(err) {
if (err) {
// We weren't able to reset the semaphore.
}
});
Retrieves a previously created semaphore or creates a new semaphore with the optionally specified number of locks in its pool.
// Create a new semaphore
pettyCache.semaphore.retrieveOrCreate('key', { size: 10 }, function(err) {
if (err) {
// Aw, snap! We couldn't create the semaphore
}
// Your semaphore was created.
});
Options
{
size: 1 || function() { var x = 1 + 1; callback(null, x); } // The number of locks to create in the semaphore's pool. Optionally, size can be a `callback(err, size)` function.
}
FAQs
A cache module for node.js that uses a two-level cache (in-memory cache for recently accessed data plus Redis for distributed caching) with some extra features to avoid cache stampedes and thundering herds.
The npm package petty-cache receives a total of 147 weekly downloads. As such, petty-cache popularity was classified as not popular.
We found that petty-cache demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.
Security News
Research
Socket's threat research team has detected five malicious npm packages targeting Roblox developers, deploying malware to steal credentials and personal data.