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

redis-registry

v1.0.5

Published

Service registry for Node.js on top of redis

Downloads

42

Readme

redis-registry

Build Status npm version

Service registry and discovery for distributed systems on top of redis and node.js

Install

npm install redis-registry

Usage

Computer 1

const registry = require('redis-registry');

const redisConfig = {
  host: '192.168.1.50',
  port: 6379
}
const services = registry(redisConfig);

// Join the registry
services.join('my-service-name', {port:8080});

Computer 2

const registry = require('redis-registry');

const redisConfig = {
  host: '192.168.1.50',
  port: 6379
}
const services = registry(redisConfig);

// Do a lookup
services.lookup('my-service-name', function(err, service) {
  console.log('Found the following service:');
  console.log(service);
});

Running the above example will produce the following output

Found the following service:
{
  name: 'my-service-name',
  port: 8080,
  hostname: '192.168.1.10',
  host: '192.168.1.10:8080',
  url: 'http://192.168.1.10:8080'
}

Note: If no hostname is passed to the join function, it will pickup the main interface IP as the hostname. If you need to use the IP of a non-primary interface, set the environment variable REGISTRY_INTERFACE to the name of the device of your choice (eth1, en1, etc)

Full api

  • services = registry(redisConfig) Create a new registry client
  • services.join(name, service, [cb]) Join the registry with a new service
  • services.leave([name], [cb]) Leave the registry.
  • services.lookup(name, cb) Lookup a single service
  • services.list([name], cb) List all services as an array. Omit the name to list all services

Services

Services are just JSON documents. redis-registry will add a default hostname and a couple of other properties. An example of a service document could be:

{
  name: 'my-service',
  port: 8080,
  hostname: '192.168.1.10',       // added by redis-registry
  host: '192.168.1.10:8080',      // added by redis-registry
  url: 'http://192.168.1.10:8080' // added by redis-registry
}

These documents are saved in redis with a TTL of 10s. Every 5s redis-registry will send an update for each service to the registry which resets the expiration counter keeping the service record. If possible you should call services.leave() before exiting your service process. Otherwise your service will be garbage collected after (at most) 10s. If your process goes down, it will automatically leave the registry (due to the TTL) and will not be discovered from other process.

License

MIT