JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 105
  • Score
    100M100P100Q88078F
  • License MIT

Metroplex is capable of transforming into a battle station, giant robot or a distributed connect client directory for Primus.

Package Exports

  • metroplex

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (metroplex) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Metroplex Build Status

Metroplex a Redis based spark/connection registry for Primus.

Installation

Metroplex is released in the npm registry and can therefor be installed using:

npm install --save metroplex

Once you've installed the module you need to tell Primus to use the plugin which is done using the primus.use method:

'use strict';

var http = require('http').createServer()
  , Primus = require('primus')
  , primus = new Primus(http, { transformer: 'sockjs' });

primus.use('metroplex', require('metroplex'));

Usage

In the example above you've seen how to add the plugin to your Primus server but not how to configure it. We have various of options that can be configured in this plugin:

  • redis: Metroplex is currently using Redis as its default back-end for storing the state of the connections. If you do not supply us with a pre-defined Redis client (or authorized) we will create a Redis client which only connects to localhost and Redis's default port number.
  • namespace: As the databases are usually shared with other programs it's good to prefix all the data that you store, in Metroplex we prefix every key with the set namespace. The default namespace is metroplex.
  • interval: We are using "alive" suffixed keys in the database to see which node process is still alive. The interval determines the interval of these updates. When the interval is reached we update the key in the database with the current EPOCH as well as start a scan for possible dead servers and removing them. The default interval 300000 ms
  • latency: The maximum time it would take to update the alive key in Redis. This time is subtracted from the set interval so we update the key BEFORE it expires. Defaults to 2000 ms.
  • address The address or public URL on which this SPECIFIC server is reachable. Should be without path name. When nothing is supplied we try to be somewhat smart and read the address and port and server type from the server that Primus is attached to and compose an URL like: http://0.0.0.0:8080 from it.

These options should be provided in the options object of the Primus server:

primus = new Primus(http, { 
  transformer: 'sockjs',
  namespace: 'metroplex',
  redis: require('redis').createClient()
});

primus.use('metroplex', require('metroplex'));

Metroplex

The orchestration is all done using the metroplex library which is bundled in this plugin. The Metroplex instance is exposed on the Primus instance when you use this plugin:

primus.metroplex.servers(function (err, servers) {
  console.log('registered servers:', servers);
});

The following public methods are available.

metroplex.servers

metroplex.servers(fn)

List all the servers in our current registry.

metroplex.servers(function (err, servers) {
  console.log(servers);
});

metroplex.spark

metroplex.spark(id, fn)

Get the server for the given spark id. It does not check if the spark on the current Primus instance. That's up to the developer to implement.

metroplex.spark(id, function (err, server) {
  console.log(server);
});

metroplex.sparks

metroplex.sparks(sparks, fn)

Get the servers for each of the ids in the given array. It will return an object and just like the metroplex.spark it does not check if spark is hosted on the current server.

License

MIT

Metroplex