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

oplog-transform

v1.1.0

Published

Tool to transfrom oplog documents into changes you can apply to other data stores

Downloads

18

Readme

build status #Oplog Transform Free your oplog

##Why? Often people want a duplicate of their data in another data store. Doing imports on an interval works but need to be scheduled. MongoDB replica sets have a tailable oplog that provides push like updates about changes happening to the records in the database. By tapping into this we can publish changes to other datastores too, keeping them up to date in real time.

oplog-transform is simply a module that provides an interface for insert, update, and remove hooks for you to fill in with how to modify the target datastore. You can then pass in oplog records and oplog-transform will use the hooks accordingly.

##Usage

Here is an example of initializing oplog-transform using an in-memory JSON object as our datastore.

var store = {}
  , Transform = require('oplog-transform')
  , transform = new Transform({
    insert: function(_id, doc, cb) {
      store[_id] = doc
      cb()
    },
    update: function(_id, done){
      done(store[_id], function(err, updatedDoc, cb) {
        store[_id] = updatedDoc
        cb()
      })
    },
    remove: function(_id, cb) {
      delete store[_id]
      cb()
    }
  })

You can write to the transform using the transform function

transform.transform(oplogDoc)

Or you can use the streaming interface to pipe oplog docs

tailedOplog.pipe(transform)

//or

transform.write(oplogDoc)

##Hooks ###insert

function(_id, doc, cb) {
  /* insert doc */
  cb()
}

The insert hook must be a function that accepts 3 parameters, the doc _id, the doc, and a callback to fire once you've inserted the document

###update

function(_id, done){
  var retrievedDoc = /* fetch doc from your secondary store */
  done(retrievedDoc, function(err, updatedDoc, cb) {
    /* store updated doc */
    cb()
  })
}

The update hook must be a function that accepts 2 parameters, the doc _id, a done callback. Once you've fetched the document from your target datastore call the done callback with the fetched document and a callback to receive an error, the updated document, and a final callback to fire once you've updated the record in your target datastore

###remove

function(_id, cb) {
  /* delete doc */
  cb()
}

The remove hook must be a function that accepts 2 parameters, the doc _id and a callback to fire once you've removed the doc.


Made with ⚡️ by @taterbase