Skip to content

A light-weight loadbalancing service discovery lib for Consul

License

Notifications You must be signed in to change notification settings

bobthemighty/disconsulate

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

64 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Disconsulate

A light-weight loadbalancing service discovery lib for Consul

Status
node

Disconsulate is an opinionated wrapper for Consul's service discovery API. It's heavily inspired by Consulite but has a few more tricks up its sleeve.

Disconsulate is built with 100% test coverage, minimal dependencies, and a tiny API.

Installation

npm install disconsulate

Usage

import Disconsulate from 'disconsulate;'

// Disconsulate uses async functions when talking to Consul.
async function fetch_database() {
  // Create a client by passing it the address of a consul server.
  // If you don't provide a server address, Disconsulate will use
  // environment variables.
  const client = new Disconsulate("http://consul.local:8500");

  // Disconsulate will raise events when a watched service changes, you can
  // use this to tear down connections, or reload config.
  client.on("change", (service) => console.log(service));

  // getService returns a promise of a registered service.
  // Disconsulate watches services in the background to automatically update
  // its cache.
  try {
      let database = await client.getService("database");

      // this second call to getService will be served from cache.
      // if there are multiple addresses available for the database service
      // Disconsulate will return each of them in turn.
      database = await client.getService("database");

      console.log(`The database is available at ${database.address}:${database.port}`);
  } catch (e) {
      // If we can't find any services, we'll raise an error at this point.
      console.log("No registration found for database", e);
  }
}

Filtering results

In some scenarios we might need to filter services by tag, query services in a separate datacentre, or search for services that are hosted on a particular class of node.

Disconsulate's getService method is able to watch multiple configurations for the same service. In the following example, we set up three separate watches which can update individually.

const client = new Disconsulate();

const live = client.getService("payment-api", {
   tags: ["live"]
});

const dev = client.getService("payment-api", {
   tags: ["dev", "feature-visa-chargebacks"],
   node: {
     "class": "CPU-optimised"
   }
});

const europe = client.getService("payment-api", {
   tags: ["live"],
   dc: "eu-west-1"
});

Retrying & Error Handling

When you first request a service, Disconsulate will have nothing in its cache, and will fetch the latest data from Consul. A failure at this point will return an error to the client.

async function fetchService() {
   const client = new Disconsulate();
   try {
     const db = await client.getService("database");
   } catch (e) {
     console.log("Failed to fetch service registration for database", e);
   }
}

Disconsulate will then keep its cache up to date using Consul's blocking queries. These queries happen in the background, automatically. If a refresh fails, Disconsulate will raise an event.

function fetchApi(){
   const client = new Disconsulate();
   client.on("error", (e) => console.log("Failed to background refresh a service"));
   return client.getService("api");
}

By default, Disconsulate will try 20 times to refresh the service before giving up. You can set the retry policy when creating a client. If Disconsulate reaches the maximum number of retries, it'll raise the "fail" event and stop retrying.

async function fetchWeb(consulAddr){
   const client = new Disconsulate(consulAddr, {
     retry: {
       maxTries: 3
     }
   });
   client.on("fail", () => console.log("Reached maximum number of retries"));
   await client.getService("web");
}

Logging

Disconsulate ships with a stub logger that logs error details to the console. You can pass your own logger to the client. A logger is any object that has the following methods:

  • debug (str)
  • info (str)
  • error (str)
  • fatal (str)
import winston from 'winston';
const logger = winston.createLogger({ level: 'error'});


function findDatabase() {
  const client = new Disconsulate({
     logger
  });
}

API

new Disconsulate(options)

Create a new instance of the Consulite class.

  • options - configuration options for managing the connection to Consul:
    • consul - consul host to connect to. Defaults to either:
      • http://${process.env.CONSUL_ADDR} or
      • http://${process.env.CONSUL_HOST}:${process.env.CONSUL_PORT} or
      • http://consul:8500 - as a last resort
    • retry: an object describing the retry policy, comprising:
      • seedWait: The minimum time to wait before retrying a failed request (default: 100 ms)
      • maxWait: The maximum delay to wait between retries (default 30,000 millisecs)
      • maxTries: The maximum number of times to retry a failed request (default: 20)
    • logger: an object exposing debug, info, error, and fatal methods.

getService(options)

Start watching a service, and return a registered address and port.

  • options: an object with the following properties
    • service: the service name as registered with Consul.
    • dc: the datacentre to search for registered services.
    • tags: an array of that must be registered on an instance, used for filtering the registered addresses.
    • node: an object of key/value pairs that will be used to filter by node metadata.

Returns a promise of a service instance { address: string, port: string, tags: [string] }

About

A light-weight loadbalancing service discovery lib for Consul

Resources

License

Stars

Watchers

Forks

Packages

No packages published