0.0.5 • Public • Published


Sophisticated, general-purpose quota management

Build Status Coverage Status Dependency Status


NPM Stats

This is a module for node.js and is installed via npm:

npm install quota --save

Use Cases for This Library

Whereever you need to respect or enforce quota limits this library can help:

  • You can respect the quota limits if you e.g. call the Twitter API. For Twitter and many other well-known API providers this library ships presets that mirror the quota limits of the API provider. This way your code will know if quota is left or how long to wait until more quota gets available without calling the provider's API that would respond with an error. Internal queueing, prioritizing, and backoff mechanisms allow using the available quota to a maximum extend without risking being categorized as abusive by the API provider.
  • You can enforce quota limits e.g. for your own API that you provide using custom API call rate limits - simple to very sophisticated - or even e.g. in office applications that limit the number of pages to print each month.

Respecting quota limits when calling an API is the most common use case and therefore Quota ships with the following presets:

These presets completely replicate the quota rules as specified by the API providers. This includes throttling and queueing .requestQuota(...) calls (see below) as well as an appropriate backoff mechanism that intervenes in case the API provider starts rejecting requests - which would be unexpected though.

Examples for the Overall Setup and Use

Quota for 1 API on a single node.js instance

var quota = require('quota');
// Create and configure the quota server which manages the quota usage.
var quotaServer = new quota.Server();
quotaServer.addManager('github'); // This is loading one of many presets.
// Create a client connected to the server locally - so no overhead involved.
var quotaClient = new quota.Client(quotaServer);
// Requesting quota for a single GitHub API call on behalf of the analog-nico user.
quotaClient.requestQuota('github', { userId: 'analog-nico' }, { requests: 1 }, { maxWait: 5000 })
    // The request is queued up to 5 seconds if no quota is available right away.
    .then(function (grant) {
        // The quota request was granted. Call the GitHub API now.
        // And afterwards tell Quota that the GitHub API call is finished.
    .catch(quota.OutOfQuotaError, function (err) {
        // The quota request was denied. Even after 5 seconds no quota became available.
        // E.g. notify the user to try again later.
    .catch(function (err) {
        // Due to technical reasons the quota request was neither granted nor denied. E.g. notify the admins.

Please refer to the particular preset you use for details about the parameters required to call .requestQuota(...) and grant.dismiss(...).

Quota for multiple APIs on a single node.js instance

var quota = require('quota');
// Create and configure the quota server which manages the quota usage.
var quotaServer = new quota.Server();
quotaServer.addManager('twitter'); // This is loading one of many presets.
quotaServer.addManager('xyzApi', myCustomQuotaManager);
// Create a client connected to the server locally - so no overhead involved.
var quotaClient = new quota.Client(quotaServer);
// You may now request the quota from each manager as needed.
quotaClient.requestQuota('twitter', /* ... */ ).then(function (grant) { /* ... */ });
quotaClient.requestQuota('xyzApi', /* ... */ ).then(function (grant) { /* ... */ });

Quota management in a cluster environment (multiple node.js instances)

This is a preview. Feature not yet implemented.

E.g. the Google Analytics API puts a limit on the overall requests per day. If you have a cluster environment with e.g. 10-20 dynamically scaled node.js instances which all do Google Analytics API calls the quota has to be managed by a single, centralized Quota server. Therefore the Quota Client supports the connection to a remote Quota Server.

Choose one node.js instance to run the Quota Server:

var quota = require('quota');
var express = require('express');
var quotaServer = new quota.Server();
quotaServer.addManager('google-analytics'); // This is loading one of many presets.
// Expose the server via a REST API
var app = express();
var server = app.listen(3000, function () {
    var host = server.address().address;
    var port = server.address().port;
    console.log('Connect your Quota Clients to http://%s:%s', host, port);

Use the following code on all node.js instances that want to request quota:

var quota = require('quota');
// Create a client connected to the remote server.
var quotaClient = new quota.Client(process.env.QUOTA_SERVER_URL);
// You may now request the quota as always.
quotaClient.requestQuota('google-analytics', /* ... */ ).then(function (grant) { /* ... */ });

Quota management in a cluster environment with local and remote Quota Servers

This is a preview. Feature not yet implemented. However, a Client can at least connect to multiple local Servers.

If the quota management is done by a remote Quota Server some overhead is introduced by the Client's REST API calls to the Server. By deploying all node.js instances in the same datacenter this overhead is minimal but can be further reduced by only running those Managers on the remote Quota Server that require centralized management. All other Managers can be moved to a local Quota Server:

var quota = require('quota');
// Create and configure the local Quota Server.
var quotaServer = new quota.Server();
quotaServer.addManager('bitly'); // Bitly puts independent limits on each IP address. So local management is sufficient.
// Create a client connected to both the local and the remote Server.
var quotaClient = new quota.Client([ quotaServer, process.env.QUOTA_SERVER_URL ]);
// When requesting quota the Client automatically finds the right Quota Server.
quotaClient.requestQuota('google-analytics', /* ... */ ).then(function (grant) { /* ... */ });
quotaClient.requestQuota('bitly', /* ... */ ).then(function (grant) { /* ... */ });

.requestQuota(...) Parameters

Description forthcoming.

grant.dismiss(...) Parameters

Description forthcoming.

Configuring Custom Quota Limits

If a preset for a certain API is not available or custom quota limits need to be enforced you can use the same API that the presets use.

Description forthcoming.


To set up your development environment for Quota:

  1. Clone this repo to your desktop,
  2. in the shell cd to the main folder,
  3. hit npm install,
  4. hit npm install gulp -g if you haven't installed gulp globally yet, and
  5. run gulp dev. (Or run node ./node_modules/.bin/gulp dev if you don't want to install gulp globally.)

gulp dev watches all source files and if you save some changes it will lint the code and execute all tests. The test coverage report can be viewed from ./coverage/lcov-report/index.html.

If you want to debug a test you should use gulp test-without-coverage to run all tests without obscuring the code by the test coverage instrumentation.

Change History

  • v0.0.5 (2015-09-30)
    • Added Pinterest preset
  • v0.0.4 (2015-09-28)
    • Implemented window-fixed throttling which is needed for the Google APIs
    • Extended all other throttling modules
  • v0.0.3 (2015-09-24)
    • Tested and improved the presets
    • Improved overall error handling
  • v0.0.2 (2015-09-22)
    • Fixed race condition that may render the maxWait option ineffective
  • v0.0.1 (2015-09-21)
    • Initial version

License (ISC)

In case you never heard about the ISC license it is functionally equivalent to the MIT license.

See the LICENSE file for details.

Package Sidebar


npm i quota

Weekly Downloads






Last publish


  • analog-nico