Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

lru-cache-for-clusters-as-promised

Package Overview
Dependencies
Maintainers
1
Versions
49
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

lru-cache-for-clusters-as-promised

LRU Cache that is safe for clusters

  • 1.0.2
  • Source
  • npm
  • Socket score

Version published
Maintainers
1
Created
Source

lru-cache-for-clusters-as-promised

lru-cache-for-clusters-as-promised Build Status Code Coverage Code Climate Issue Count Dependency Status Dev Dependency Status Downloads

LRU Cache for Clusters as Promised provides a cluster-safe lru-cache via Promises. For environments not using cluster, the class will provide a Promisified interface to a standard lru-cache.

Each time you call cluster.fork(), a new thread is spawned to run your application. When using a load balancer even if a user is assigned a particular IP and port these values are shared between the workers in your cluster, which means there is no guarantee that the user will use the same workers between requests. Caching the same objects in multiple threads is not an efficient use of memory.

LRU Cache for Clusters as Promised stores a single lru-cache on the master thread which is accessed by the workers via IPC messages. The same lru-cache is shared between workers having a common master, so no memory is wasted.

To differentiate caches on the master as instances on the workers, specify a namespace value in the options argument of the new LRUCache(options) constructor.

install

npm install --save lru-cache-for-clusters-as-promised

example usage

const LRUCache = require('lru-cache-for-clusters-as-promised');
const cache = new LRUCache({
  max: 50,
  stale: false,
  namespace: 'users',
});

const user = { name: 'user name' };
const key = 'userKey';

// set a user for a the key
cache.set(key, user)
.then(() => {
  console.log('set the user to the cache');

  // get the same user back out of the cache
  return cache.get(key);
})
.then((cachedUser) => {
  console.log('got the user from cache', cachedUser);

  // check the number of users in the cache
  return cache.length();
})
.then((size) => {
  console.log('user cache size/length', size);

  // remove all the items from the cache
  return cache.reset();
})
.then(() => {
  console.log('the user cache is empty');

  // return user count, this will return the same value as calling length()
  return cache.itemCount();
})
.then((size) => {
  console.log('user cache size/itemCount', size);
});

options

  • namespace: string
    • the namespace for this cache on the master thread as it is not aware of the worker instances
  • max: number
    • the maximum items that can be stored in the cache
  • maxAge: milliseconds
    • the maximum age for an item to be considered valid
  • stale: true|false
    • when true expired items are return before they are removed rather than undefined

! note that length and dispose are missing as it is not possible to pass functions via IPC messages.

api

  • set(key, value)
    • sets a value for a key
  • get(key)
    • returns a value for a key
  • peek(key)
    • return the value for a key without updating its last access time
  • del(key)
    • remove a value from the cache
  • has(key)
    • returns true if the key exists in the cache
  • reset()
    • removes all values from the cache
  • keys()
    • returns an array of all the cache keys
  • values()
    • returns an array of all the cache values
  • dump()
    • returns a serialized array of the cache contents
  • prune()
    • manually removes items from the cache rather than on get
  • length()
    • return the number of items in the cache
  • itemCount()
    • return the number of items in the cache. same as length().

process flow

Clustered cache on master thread for clustered environments*

                                                                +-----+
+--------+  +---------------+  +---------+  +---------------+   # M T #
|        +--> LRU Cache for +-->         +--> Worker Sends  +--># A H #
| Worker |  |  Clusters as  |  | Promise |  |  IPC Message  |   # S R #
|        <--+   Promised    <--+         <--+   to Master   <---# T E #
+--------+  +---------------+  +---------+  +---------------+   # E A #
                                                                # R D #
v---------------------------------------------------------------+-----+
+-----+
* W T *   +--------------+  +--------+  +-----------+
* O H *--->   Master     +-->        +--> LRU Cache |
* R R *   | IPC Message  |  | Master |  |    by     |
* K E *<--+  Listener    <--+        <--+ namespace |
* E A *   +--------------+  +--------+  +-----------+
* R D *
+-----+

Promisified for non-clustered environments*

+---------------+  +---------------+  +---------+  +-----------+
|               +--> LRU Cache for +-->         +-->           |
| Non-clustered |  |  Clusters as  |  | Promise |  | LRU Cache |
|               <--+   Promised    <--+         <--+           |
+---------------+  +---------------+  +---------+  +-----------+

Keywords

FAQs

Package last updated on 26 Aug 2016

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc