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

cache-proxy-plus

v1.3.0

Published

A method proxy library that makes it easy to implement local and remote cache with built-in usage statistics.

Downloads

7

Readme

Cache Proxy Plus build-status npm license

English | 简体中文

Overview

A Node.js library for executing proxy methods with ease, combining local and remote caching, with usage statistics output and written in TypeScript.

Features

  1. Supports ES Module only, not compatible with commonjs
  2. Method proxy supports AsyncFunction only
  3. Avoids cache breakdown; when the cache expires, it won't concurrently send requests to the backend service
  4. Supports background polling updates to ensure the cache is always valid and up-to-date
  5. Supports fallback cache, even if the remote service crashes and the cache has expired, it can still retrieve cached content
  6. Supports remote cache, such as Redis
  7. Supports caching usage statistics

Cache Priority

In-process cache (local cache) --> Remote cache --> Fallback priority cache --> Actual call --> Fallback cache

As shown in the diagram:

/async-cache-plus

Usage Guide

Install Dependencies

npm i cache-proxy-plus
// or
pnpm add cache-proxy-plus

Basic Usage

import { cacheProxyPlus } from 'cache-proxy-plus'

class Base {
  async doBase(id) {
    const res = Math.random(id)
    return res
  }
}

class Manager extends Base {
  async doJob(id) {
    const res = Math.random()
    return res
  }
}

const manager = new Manager()
const managerProxy = cacheProxyPlus(manager, { ttl: 2000, statsInterval: 1000 * 10 })
managerProxy.channel.on('stats', s => console.info(s))

setInterval(async () => {
  const res1 = await managerProxy.doJob(1)
  const res2 = await managerProxy.doJob(2)
  const res3 = await managerProxy.doBase(3)
}, 1000)

When importing, you can also use cacheProxy instead of cacheProxyPlus.

Parameter

cacheProxyPlus(target, options)

target:

  • Class object containing AsyncFunction

options:

  • exclude: (default: []) Exclude methods that do not require caching proxies, string array
  • ttl: (default: 1000 * 60) Expiration time of the cache in milliseconds
  • checkPeriod: (default: 1000) Time interval to check cache expiration in milliseconds
  • statsInterval: (default: 1000 * 60) Interval for printing cache usage statistics in milliseconds
  • randomTtl: (default: false) Whether to add random timeout; calculated as: ttl * (0.8 + 0.3 * Math.random())
  • methodTtls: (default: null) Configure timeout for specific methods, as an Object.
    • [methodName]: (default: 1000 * 60) Cache expiration time for a specific method in milliseconds
  • subject: (default: [target.constructor.name]) Subject used as key prefix to differentiate keys for the same method of different targets.
    • Note: Cannot be a random string, or the key will be different after restarting
  • fallback: (default: false) Whether to use fallback cache; the fallback cache will save the last successfully retrieved value. When both local and asyncCache are invalid, and a real call fails, it retrieves the value from the fallback cache.
  • fallbackTtl: (default: 1000 * 60 * 60) Expiration time of the fallback cache in milliseconds
  • fallbackMax: (default: 1000 * 10) Maximum number of keys the fallback cache can store, using LRU strategy
  • fallbackFirst: (default: false) Prioritize using fallback cache, asynchronously execute update, so it doesn't wait for the real update to complete.
  • bgUpdate: (default: false) Whether to support background polling updates of key values
  • bgUpdateDelay: (default: 100) Waiting time between updating two keys in the background
  • bgUpdatePeriodDelay: (default: 1000 * 5) After a round of background polling updates, how long to wait before the next round of updates
  • bgUpdateExpired: (default: 1000 * 60 * 60) After how long a key has not been accessed, stop background updates for that key
  • concurrency: (default: 10) Total concurrency limit for real requests, including all methods, to avoid excessive impact on the backend
  • remoteCache: (default: null) Asynchronous cache object, can implement the use of external caches such as Redis and memcached, must inherit the base class RemoteCache

Remote Cache

Using remote cache requires inheriting the base class RemoteCache, relevant code: RemoteCache

Below is an example using Redis as the remote cache:

import { RemoteCache } from 'cache-proxy-plus'

class RedisCache extends RemoteCache {
  private redis = new Redis()
  constructor() {
    super()
  }

  async set(key: string, value: any, ttl: number) {
    const wrapped = { value }
    return this.redis.set(key, JSON.stringify(wrapped), 'PX', ttl + 100)
  }

  async get(key: string) {
    const wrapped = await this.redis.get(key)
    return wrapped ? JSON.parse(wrapped).value : null
  }

  quit() {
    this.redis.disconnect()
    this.redis.quit()
  }
}

Clear Cache

There are two scenarios: one is to clear all local caches, and the other is to clear the local cache for a specific method in the proxy.

// clear all local caches
managerProxy.channel.clear()

// clear local cache for a specific method
managerProxy.channel.clear(methodName)

Event

managerProxy.channel.on('eventName', () => {})

eventName can be: stats, bg.stats, bg.break.off, error, and expired

Error

managerProxy.channel.on('error', err => {
  // background error
})

Expired Key

managerProxy.channel.on('expired', (key, type) => {
  // type: expired or fallbackExpired
})

Usage Statistics

stats contains current, total, and methods

// Default output every minute
managerProxy.channel.on('stats', stats => {
  const {
    current, // Statistics for the last minute
    total, // Total statistics since the process started
    methods // Individual statistics for each method
  } = stats
  // ...
})

Details for each statistic:

{
  local: 0, // Number of hits in local cache
  remote: 0, // Number of hits in remote cache
  update: 0, // Number of actual requests made
  miss: 0, // Number of cache misses
  expired: 0, // Number of local cache expirations
  failed: 0, // Number of request errors
  wait: 0, // Number of successful concurrent waits
  failedWait: 0, // Number of errors in concurrent waits
  background: 0, // Number of background updates
  failedBackground: 0, // Number of errors in background updates
  fallback: 0, // Number of hits in fallback cache
  fallbackFirst: 0, // Number of hits prioritizing fallback cache
  fallbackExpired: 0, // Number of fallback cache expirations
}

Another way to obtain statistics:

const stats = managerProxy.channel.stats()

Background

Update Statistics

managerProxy.channel.on('bg.stats', stats => {
  // stats details
  // stats.cycleTime: Time for a complete update cycle
  // stats.delayTime: Pause time for a complete update cycle
  // stats.updateTime: Asynchronous waiting time for a complete update cycle
  // stats.updatedSize: Total number of keys updated in a complete update cycle
})

Keys Removed Due to Long Inactivity

managerProxy.channel.on('bg.break.off', key => {
  // ...
})

License

Released under the MIT License.