MQTT | NATS Docs
MQTT support in NATS is intended to be an enabling technology allowing users to leverage existing investments in their IoT deployments. Updating software on the edge or endpoints can be onerous and risky, especially when embedded applications are involved.
Configuration | NATS Docs
MQTT requires a server name to be set. Server names must be unique in a cluster or super-cluster topology. The server name is set in the top-level section of the server configuration. Here is an example: server_name: "my_mqtt_server" mqtt { port: 1883 ...
Compare NATS | NATS Docs
NATS supports WebSockets, a Kafka bridge, an IBM MQ Bridge, a Redis Connector, Apache Spark, Apache Flink, CoreOS, Elastic, Elasticsearch, Prometheus, Telegraf, Logrus, Fluent Bit, Fluentd, OpenFAAS, HTTP, and MQTT, and more.
Welcome | NATS Docs
NATS is a simple, secure and high performance open source data layer for cloud native applications, IoT messaging, and microservices architectures. We feel that it should be the backbone of your communication between services.
WebSocket | NATS Docs
WebSocket. Supported since NATS Server version 2.2. WebSocket support can be enabled in the server and may be used alongside the traditional TCP socket connections. TLS, compression and Origin Header checking are supported.
NATS 2.2 | NATS Docs
The 2.2 release provides highly scalable, highly performant, secure and easy-to-use next generation streaming in the form of JetStream, allows remote access via websockets, has simplified NATS account management, native MQTT support, and further enables NATS toward our goal of securely democratizing streams and services for the hyperconnected ...
Monitoring | NATS Docs
The NATS monitoring endpoints support JSONP and CORS, making it easy to create single page monitoring web applications. Part of the NATS ecosystem is a tool called nats-top that visualizes data from these endpoints on the command line.
Configuring NATS Server
The standard way of configuring the NATS server product is through a configuration file. We use a simple configuration format that combines the best of traditional formats and newer styles such as JSON and YAML.
NATS and Docker | NATS Docs
The following steps illustrate how to run a server with the ports exposed on a docker network. First, create the docker network 'nats:'. docker network create nats. Then start the server: docker run --name nats --network nats --rm -p 4222:4222 -p 8222:8222 nats --http_port 8222.
Configuring JetStream | NATS Docs
Multi-tenancy & Resource Mgmt. JetStream is compatible with NATS 2.0 Multi-Tenancy using Accounts. A JetStream enabled server supports creating fully isolated JetStream environments for different accounts. This will dynamically determine the available resources.