A simple service mesh. Messages sent within the service mesh can be consistently partitioned across members of the cluster.

npm install meshage --save

Initialize some nodes and define a handler for a subject & message:

const {mesh, nats} from 'meshage';
const n1 = mesh(nats('nats://localhost:4222'));

await n1.subject('something')
    .on(SomeMessage, (message: SomeMessage) => {
        return 'reply';
    })
    .awaitRegistration();

const reply = await mesh(nats('nats://localhost:4222'))
    .subject('something')
    .send(new SomeMessage(), {
        wait: true | false, // Whether to wait for a reply or just fire the message.
        timeout: 1000 // Time in milliseconds to wait for a reply.
    });

To enable consistent hashing / partitioned message support one node in the "cluster" should be configured with the monitorUrl for the nats servers where subscription information can be obtained from. This will cause the node to periodically broadcast subscription data used to consistently hash & partition requests:

const n1 = mesh(nats({
    server: 'nats://localhost:4222',
    monitorUrl: 'http://localhost:8222'
}));

Messages may also optionally be sent & received with an HTTP listener by wrapping the supplied backend:

const {mesh, nats, http} from 'meshage';
const n1 = mesh(http(nats('nats://localhost:4222'), 8080));
n1.subject('something')
    .on(SomeMessage, (message: SomeMessage) => {
        return 'reply';
    });

Sends a message to be handled by a registered handler for the specified subject/message.

Path : /api/:subject/:partitionKey?

Path params :

• subject - The logical name for the message handler subject.
• partitionKey - (Optional) Identifier used to consistently partition the request to known handlers.

Query params:

• messageName - (Dependant) The name of message. If the messageName is not supplied via this param, then it must be provided in the message body as a top-level key called name - e.g. {"name": "SomeMessage", ...}
• wait - (Optional) Whether to wait for a reply or just fire the message.
• timeout - (Optional) Time in milliseconds to wait for a reply.

Example:

Request:

curl -sX POST http://localhost:8080/api/some-subject/$RANDOM?messageName=echo \
     -H 'Content-Type: application/json' \
     -d '{"hello":"world"}'

Response:

{
  "echoed": {
    "hello": "world"
  }
}

Sends a message to all registered handlers for the specified subject/name pair.

URL : /api/broadcast/:subject

Path params :

• subject - The logical name for the message handler subject.

Query params:

• messageName - (Dependant) The name of message. If the messageName is not supplied via this param, then it must be provided in the message body as a top-level key called name - e.g. {"name": "SomeMessage", ...}
• wait - (Optional) Whether to wait for a reply or just fire the message.
• timeout - (Optional) Time in milliseconds to wait for replies. Replies not received before the timeout of omitted.

Example :

Request:

curl -sX POST http://localhost:8080/api/broadcast/some-subject?messageName=echo \
     -H 'Content-Type: application/json' \
     -d '{"hello":"world"}'

Response:

[
 {
   "echoed": {
     "hello": "world"
   }
 }, 
 {
   "echoed": {
     "hello": "world"
   }
 }
]

MIT