Displaying 1 to 20 from 61 results

ruby-nats - Ruby client for NATS, the cloud native messaging system.

  •    Ruby

A Ruby client for the NATS messaging system.If you're looking for a non-EventMachine alternative, check out the nats-pure gem.

nats.go - Golang client for NATS, the cloud native messaging system.

  •    Go

A Go client for the NATS messaging system. NATS servers have a new security and authentication mechanism to authenticate with user credentials and Nkeys. The simplest form is to use the helper method UserCredentials(credsFilepath).

nats.js - Node.js client for NATS, the cloud native messaging system.

  •    Javascript

A Node.js client for the NATS messaging system. The json connect property makes it easier to exchange JSON data with other clients.

nats.rb - Ruby client for NATS, the cloud native messaging system.

  •    Ruby

A Ruby client for the NATS messaging system. If you're looking for a non-EventMachine alternative, check out the nats-pure gem.




node-nats - Node.js client for NATS, the cloud native messaging system.

  •    Javascript

A Node.js client for the NATS messaging system.See examples and benchmarks for more information..

hemera - 🔬 Writing reliable & fault-tolerant microservices with https://nats.io

  •    Javascript

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 provide a pattern matching RPC style. You don't have to worry about the transport. NATS is powerful.Hemera has not been designed for high performance on a single process. It has been designed to create lots of microservices doesn't matter where they live. It choose simplicity and reliability as primary goals. It act together with NATS as central nervous system of your distributed system. Transport independency was not considered to be a relevant factor. In addition we use pattern matching which is very powerful. The fact that Hemera needs a broker is an argument which should be taken into consideration when you compare hemera with other frameworks. The relevant difference between microservice frameworks like senecajs, molecurer is not the performance or modularity its about the complexity you need to manage. Hemera is expert in providing an interface to work with lots of services in the network, NATS is the expert to deliver the message at the right place. Hemera is still a subscriber of NATS with some magic in routing and extensions. We don't have to worry about all different aspects in a distributed system like routing, load-balancing, service-discovery, clustering, health-checks ...

liftbridge - Lightweight, fault-tolerant message streams.

  •    Go

Liftbridge provides lightweight, fault-tolerant message streams by implementing a durable stream augmentation for the NATS messaging system. It extends NATS with a Kafka-like publish-subscribe log API that is highly available and horizontally scalable. Use Liftbridge as a simpler and lighter alternative to systems like Kafka and Pulsar or use it to add streaming semantics to an existing NATS deployment. See the introduction post on Liftbridge and this post for more context and some of the inspiration behind it.


vlan-nats - Virtual LAN over NATS

  •    Go

Disclaimer: This is only a fun experiment. Do not use it for anything serious. vlan-nats creates a virtual LAN using NATS. Backed by a NATS server (or cluster), vlan-nats can create and run a network interface that is connected to a virtual L2 switch.

nats.java - Java client for NATS

  •    Java

A Java client for the NATS messaging system. This is version 2.x of the java-nats library. This version is a ground up rewrite of the original library. Part of the goal of this re-write was to address the excessive use of threads, we created a Dispatcher construct to allow applications to control thread creation more intentionally. This version also removes all non-JDK runtime dependencies.

nats.net - The official C# Client for NATS

  •    CSharp

A C# .NET client for the NATS messaging system. This NATS Maintainer supported client parallels the NATS GO Client.

asyncio-nats - An asyncio based Python client for NATS

  •    Python

An asyncio-based (PEP 3156) Python client for the NATS messaging system.Should be compatible with at least Python 3.4 and Python +3.5.1 using gnatsd as the server.

csharp-nats - The official C# Client for NATS

  •    CSharp

A C# .NET client for the NATS messaging system.This Apcera supported client parallels the NATS GO Client.

nats-top - Top like program monitor for NATS.

  •    Go

nats-top is a top-like tool for monitoring NATS servers.Monitoring http and https ports from the NATS server.

node-nats-streaming - Node.js client for NATS Streaming

  •    Javascript

Node NATS Streaming is an extremely performant, lightweight reliable streaming platform powered by NATS for Node.js.NATS Streaming subscriptions are similar to NATS subscriptions, but clients may start their subscription at an earlier point in the message stream, allowing them to receive messages that were published before this client registered interest.

prometheus-nats-exporter - A Prometheus exporter for NATS metrics

  •    Go

The Prometheus NATS Exporter consists of both a package and an application that exports NATS server metrics to Prometheus for monitoring. The exporter aggregates metrics from the server monitoring endpoints you choose (varz, connz, subsz, routez) from a NATS server into a single Prometheus exporter endpoint.Start the prometheus-nats-exporter executable, and poll the varz metrics endpoints of the NATS server located on localhost configured with a monitor port of 5555.

python-nats - A Python 2 client for NATS

  •    Python

A Python async client for the NATS messaging system.Copyright (c) 2015-2017 Apcera Inc.