A memory store for the
express-rate-limit
middleware made for use with the
node.js cluster module.
npm install @express-rate-limit/cluster-memory-store(Alternate installation methods - pnpm, yarn, Github Releases, etc.)
This package requires you to use Node 16 or above.
In the cluster primary:
import { ClusterMemoryStorePrimary } from '@express-rate-limit/cluster-memory-store'
const rateLimiterStore = new ClusterMemoryStorePrimary()
rateLimiterStore.init()In each cluster worker:
import { rateLimit } from 'express-rate-limit'
import { ClusterMemoryStoreWorker } from '@express-rate-limit/cluster-memory-store'
const limiter = rateLimit({
store: new ClusterMemoryStoreWorker(),
/* ...*/
})
app.use(limiter)See the example/ folder for a
complete, working example.
ClusterMemoryStoreWorker takes an optional configuration object with the
following options:
string
When applying multiple rate limits (e.g. a global limit and a more strict limit for a specific endpoint), set this to a unique value on each to prevent double-counting of visits.
Because this store requires code execution in the primary process, it doesn't
work with process managers that need full control of the primary process,
including PM2 when in cluster mode.
To work with PM2, use the following configuration:
instances: 1,
exec_mode: 'fork',
And then edit your main JS file to include the clustering code, similar to this example.
This looses some of the benefits of using PM2, because it can no longer directly manage worker processes.
Gatling is not currently compatibile
with cluster-memory-store.
If you encounter a bug or want to see something added/changed, please go ahead and open an issue! If you need help with something, feel free to start a discussion!
If you wish to contribute to the library, thanks! First, please read the contributing guide. Then you can pick up any issue and fix/implement it!
MIT © Nathan Friedly and Vedant K
