The hemera from enterstudio

A Node.js microservices toolkit for the NATS messaging system

Node: 4.x, 5.x, 6.x, 7.x
Documentation: https://hemerajs.github.io/hemera/
Website: https://hemerajs.github.io/hemera-site/
Lead Maintainer: Dustin Deus

📓 Getting Started

Hemera (/ˈhɛmərə/; Ancient Greek: Ἡμέρα [hɛːméra] "day") is a small wrapper around the NATS driver. NATS is a simple, fast and reliable solution for the internal communication of a distributed system. It chooses simplicity and reliability over guaranteed delivery. We want to provide a toolkit to develop micro services in an easy and powerful way. We use bloom filters to provide a pattern matching RPC style. You don't have to worry about the transport. NATS is powerful.

With Hemera you have the best of both worlds. Efficient pattern matching to have the most flexibility in defining your RPC's. It doesn't matter where your server or client lives. You can add the same add as many as you want on different hosts to ensure maximal availability. The only dependency you have is a single binary of 7MB. Mind your own business NATS do the rest for you:

The key features of NATS in combination with Hemera are:

Lightweight: The Hemera core is small as possible and can be extended by extensions or plugins.
Location transparency: A service may be instantiated in different locations at different times. An application interacting with an service and does not know the service physical location.
Service Discovery: You don't need a service discovery all subscriptions are managed by NATS.
Load Balancing: Requests are load balanced (random) by NATS mechanism of "queue groups".
Packages: Providing reliable and modern plugins to the community.
High performant: NATS is able to handle million of requests per second.
Scalability: Filtering on the subject name enables services to divide work (perhaps with locality) e.g. topic:auth:germany. Queue group name allow load balancing of services.
Fault tolerance: Auto-heals when new services are added. Configure cluster mode to be more reliable.
Auto-pruning: NATS automatically handles a slow consumer and cut it off.
Pattern driven: Define the signatures of your RPC's in JSON and use the flexibility of pattern-matching.
PubSub: Hemera supports all features of NATS. This includes wildcards in subjects and normal publish and fanout mechanism.
Tracing: Any distributed system need good tracing capabilities. We provide support for Zipkin a tracing system which manages both the collection and lookup of this data.
Monitoring: Your NATS server can be monitored by cli or a dashboard.
Payload validation: Create your own validator or use existing plugins for Joi and Parambulator.
Serialization: Use JSON, Msgpack or Avro to serialize your data (dynamic or static).
Metadata: Transfer metadata across services or attach contextual data to tracing systems.
Dependencies: NATS is a single binary of 7MB and can be deployed in seconds.

What Hemera code looks like

const Hemera = require('nats-hemera')
const HemeraJoi = require('hemera-joi')
const nats = require('nats').connect(authUrl)

const hemera = new Hemera(nats, { logLevel: 'info' })
hemera.use(HemeraJoi)

hemera.ready(() => {

  let Joi = hemera.exposition['hemera-joi'].joi

  hemera.add({ 
    topic: 'math',
    cmd: 'add',
    a: Joi.number().required(),
    b: Joi.number().required()
  }, (req, cb) => {
    cb(null, req.a + req.b)
  })

  hemera.act({ 
    topic: 'math',
    cmd: 'add',
    a: 1,
    b: 2
  }, (err, resp) => {
    hemera.log.info(resp)
  })

})

Documentation

There is an extensive documentation or look in the Examples.

Get Involved

Contributing: Pull requests are welcome!
- Read CONTRIBUTING.md and check out our help-wanted issues
- Submit github issues for any feature enhancements, bugs or documentation problems
Support: Join our gitter chat to ask questions to get support from the maintainers and other Hemera developers
- Questions/comments can also be posted as github issues
Discuss: Tweet using the #HemeraJs hashtag