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

pouchdb-commit-log

v0.3.0

Published

cluster-friendly append-only topic-based commit log + materialized view implementation for pouchdb (inspired by apache kafka and samza)

Downloads

3

Readme

pouchdb-commit-log build status

cluster-friendly append-only topic-based commit log + materialized view implementation for pouchdb (inspired by apache kafka and samza)

Example

var Pouch = require('pouchdb')
var CommitLog = require('pouchdb-commit-log')
var assert = require('assert')

var db = new Pouch('testdb', {db: require('memdown')})

CommitLog(db, 'a')

db1.append('letters', {name: 'a'}).then(function () {
  return db1.append('letters', {name: 'b'})
}).then(function () {
  return db1.append('letters', {name: 'c'})
}).then(function () {
  return db1.getTopic('letters')
}).then(function (res) {
  var values = res.rows.map(function (row) { return row.doc.name })
  assert.deepEqual(values, ['a', 'b', 'c'])
})

Method

Messages appended to the log are sorted by topic, then monotonic-timestamp, then nodeid. This method provides reasonably accurate insert order provided that the clocks on all nodes in a cluster are set correctly.

Usage

CommitLog(db, nodeid)

nodeid must be unique within the cluster. Adds the following methods to the provided db instance:

  • append
  • getTopic
  • view
  • materializedView
  • watchView

This will also add an event emitter at db.topics.

db.topics.on('numbers', function (change) {
  // emitted any time a message is appended to the `numbers` topic
  // `change` is the pouchdb change that triggered the event
})

db.append(topic, doc, callback)

Adds doc to the topic log. callback receives the error and/or response from the pouchdb insert operation. doc must be an object. It is a convention to only use topic names that match /[a-zA-Z0-9-_\.]+/ and always start with an alphanumeric character.

db.getTopic(topic, callback)

Get all messages that have been appended to this topic. callback receives the error and/or response from the pouchdb request.

db.view(topics, transform, callback)

topics can be a single string name for a topic or an array of strings for multiple topics. For each topic, all messages will be passed as one argument to the transform function. callback receives any error that occurs and the value returned by the transform function.

db.view(['numbers', 'letters'], function (numbers, letters) {
  return numbers.rows.reduce(function (acc, h) {
    return acc + parseInt(h.doc.name)
  }, 0) + letters.rows.reduce(function (acc, h) {
    return acc + h.doc.name
  })
}, function (err, res) {
  // previously, these messages were appended to the 'numbers' topic
  // {name: 1}, {name: 2}, {name: 3}
  //
  // and these messages were appended to the 'letters' topic
  // {name: 'a'}, {name: 'b'}, {name: 'c'}
  assert.notOk(err)
  assert.equal(res, '6abc')
})

db.materializedView(name, topics, transform, callback)

Same behavior as view but instead of passing the result of transform to callback, it is saved with the _id name in the pouchdb database. transform must return a json object so the value can be saved. name must not fall within any topic lexographically. The convention is to prefix materialized view names with -.

db.materializedView('-sum', 'numbers', function (numbers) {
  return {
    value: numbers.rows.reduce(function (acc, h) {
      return acc + parseInt(h.doc.name)
    }, 0)
  }
}, function (err, res) {
  // previously, these messages were appended to the 'numbers' topic
  // {name: 1}, {name: 2}, {name: 3}
  assert.notOk(err)
  assert.ok(res.ok)

  db.get('-sum', function (err, doc) {
    assert.equal(doc.value, 6)
  })
})

db.watchView(name, topics, transform, options)

Same behavior as materializedView but the saved document is updated any time a message is appended to the a one of the required topics.

options.throttle = 1000 // default control the maximum frequency the materialized view will be saved.

// `-sum` will be updated any time db.append('numbers', { ... }) is called
db.watchView('-sum', 'numbers', function (res) {
  return {
    value: res.rows.reduce(function (acc, h) {
      return acc + parseInt(h.doc.name)
    }, 0)
  }
})