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

vip

v0.1.4

Published

very important process - use etcd to avoid a split brain across a cluster

Downloads

445

Readme

vip

vip (very important process) is a module that uses a distributed lock module locked to ensure that only one copy of a function is running across a cluster

This is useful to avoid a split brain when running some kind of cluster wide co-ordination process

It uses etcd which uses the raft protocol

install

$ npm install vip

usage

Create a new vip function that will run only once on the elected node:

var vip = require('vip')

// pass the etcd connection string 
var vipcontroller = vip('127.0.0.1:4001,127.0.0.1:4002')

// this can also be an etcdjs object
var vipcontroller = vip(etcdjs('127.0.0.1:4001,127.0.0.1:4002'))

// create a candidate passing the key path and node name
var httpRouter = vipcontroller({
	path:'/http_router',
	id:'node1',
	value:'apples',
	ttl:10
}, function(){

	// here we start the router
	// this code will only ever have one copy running across the cluster

})

httpRouter.on('select', function(id, value){
	// this is run only on the node that was elected
})

httpRouter.on('change', function(id, value){
	// this is run across all nodes
})

httpRouter.start()

api

var vipcontroller = vip(etcdhosts)

Create a controller that is connected to some etcd peers

var service = vipcontroller(opts, fn)

Create a new candidate function - opts is an object with the following keys:

  • id - the id of this node
  • path - the key path used to co-ordinate the lock
  • value - the value associated with the node (can be any string)
  • ttl - the time to live used by the locking module

fn is executed once and only when the node is elected as the current leader for the service across the cluster

events

service.on('select', function(value){})

This event is triggered when the node has been elected and it's value distributed to the cluster.

You can run logic in this function that should only be running on one server at a time.

service.on('change', function(value, nodeid){})

This event is triggered when the lock value has changed regardless of which node was elected.

The nodeid is of the elected machine is passed as the second argument.

license

MIT