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

@textile/datastore-ttl

Package Overview
Dependencies
Maintainers
4
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@textile/datastore-ttl

An implementation of the Datastore interface that supports a time-to-live for key-value pairs.

  • 0.0.5
  • latest
  • Source
  • npm
  • Socket score

Version published
Maintainers
4
Created
Source

Time to Live Datastore (datastore-ttl)

Made by Textile Chat on Slack GitHub license GitHub package.json version npm (scoped) Release Docs Workflow standard-readme compliant

An implementation of the Datastore interface that supports a time-to-live (TTL) for key-value pairs.

After the TTL expires on a given key, the entry will be automatically cleared from the datastore unless it is refreshed in the mean time. In this way you can build utilities like session managers where a given session is refreshed with each interaction but expires after a set period of time since the last interaction. This library borrows inspiration and ideas from level-ttl.

Table of Contents

Click to expand

Background

TTLDatastore 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 frequency option to the constructor.

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 frequency. Note though that a scan only involves invoking a query that returns only the entries due to expire, so it doesn't have to manually check through all entries with a TTL. Depending on the backing Datastore, this could be reasonably efficient, or extremely slow. So keep that in mind.

Default TTL

You can set a default TTL value for all your keys by specifying the ttl option to the constructor. This can be overridden by explicitly setting the TTL value on put or by calling the top-level ttl method.

Install

npm i @textileio/datastore-ttl

Usage

import { Buffer } from 'buffer'
import { MemoryDatastore, Key } from 'interface-datastore'
import { TTLDatastore } from '@textile/datastore-ttl'

// Simple promise-based sleep function
const sleep = (ms: number) => new Promise(r => setTimeout(r, ms))

// Use any compliant Datastore
const child = new MemoryDatastore()
const key = new Key('foo')
const store = new TTLDatastore(child)
await ttl.put(key, Buffer.from('bar'), 1000)
// Wait 900 ms...
await sleep(900)
// Keep alive for another 100 ms from now
await ttl.ttl(key, 100)
await ttl.has(key) // true
await ttl.expiration(key) // <unix-timestamp>
await ttl.get(key) // <Buffer>
// Wait 110 ms
await sleep(110)
await ttl.has(key) // false

There are also several useful examples included in the tests.

API

See https://textileio.github.io/js-datastore-ttl

Maintainers

Carson Farmer

Contributing

See the contributing file. PRs accepted!

Small note: If editing the README, please conform to the standard-readme specification.

License

MIT (c) 2019 Textile.io

Thanks

Big thanks to the find folks behind Level/level-ttl.

Keywords

FAQs

Package last updated on 03 Jan 2020

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