Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Add a 'ttl' (time-to-live) option to LevelUP for put() and batch()

tag: 0.2.0

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 .gitignore initial commit April 20, 2013
Octocat-spinner-32 .jshintrc @0.2.0 release June 20, 2013
Octocat-spinner-32 .travis.yml travisify April 20, 2013
Octocat-spinner-32 LICENSE initial commit April 20, 2013
Octocat-spinner-32 level-ttl.js
Octocat-spinner-32 package.json
Octocat-spinner-32 test.js

Level TTL Build Status

LevelDB Logo

Add a 'ttl' (time-to-live) option to LevelUP for put() and batch()

Augment LevelUP to handle a new 'ttl' option on put() and batch() that specifies the number of milliseconds an entry should remain in the data store. After the TTL, the entry will be automatically cleared for you.

var levelup = require('levelup')
  , ttl     = require('level-ttl')

levelup('/tmp/foo.db', function (err, db) {
  db = ttl(db)

  // --------------------------- put() --------------------------- //
  // this entry will only stay in the data store for 1 hour
  db.put('foo', 'bar', { ttl: 1000 * 60 * 60 }, function (err) { /* .. */ })

  // -------------------------- batch() -------------------------- //
  // the two 'put' entries will only stay in the data store for 1 hour
      { type: 'put', key: 'foo', value: 'bar' }
    , { type: 'put', key: 'bam', value: 'boom' }
    , { type: 'del', key: 'w00t' }
  ], { ttl: 1000 * 60 * 60 }, function (err) { /* .. */ })

If you put the same entry twice, you refresh the TTL to the last put operation. In this way you can build utilities like session managers for your web application where the user's session is refreshed with each visit but expires after a set period of time since their last visit.

Level TTL uses an internal scan every 10 seconds by default, this limits the available resolution of your TTL values, possibly delaying a delete for up to 10 seconds. The resolution can be tuned by passing the 'checkFrequency' option to the ttl() initialiser.

levelup('/tmp/foo.db', function (err, db) {
  // scan for deletables every second
  db = ttl(db, { checkFrequency: 1000 })

  /* .. */

Of course, a scan takes some resources, particularly on a data store that makes heavy use of TTLs. If you don't require high accuracy for actual deletions then you can increase the 'checkFrequency'. Note though that a scan only involves invoking a LevelUP ReadStream that returns only the entries due to expire, so it doesn't have to manually check through all entries with a TTL. As usual, it's best to not do too much tuning until you have you have something worth tuning!


Level TTL is Copyright (c) 2013 Rod Vagg @rvagg and licensed under the MIT licence. All rights not explicitly granted in the MIT license are reserved. See the included LICENSE file for more details.

Something went wrong with that request. Please try again.