NATS Connection String Builder

NATS is a lightweight, high-performance open-source messaging system for cloud-native applications. It supports publish-subscribe, request-reply, and queue subscriber patterns. NATS is known for its simplicity — a minimal server with no dependencies — and extremely low latency (sub-millisecond in LAN environments).

nats:// connects to a NATS server over plain TCP (default port 4222). tls:// (or nats:// with TLS options) connects over TLS/SSL. For production deployments, always use TLS to encrypt messages in transit. NATS Leafnode and Gateway connections typically also use TLS.

NATS supports token authentication as an alternative to username/password. The server is configured with auth_token (or multiple tokens). Clients connect with a single token string. Token auth is simpler than user/pass for machine-to-machine connections but offers less granular access control than NKeys or JWT-based auth.

In cluster mode, multiple NATS servers form a cluster and route messages between each other. Clients can provide a list of server URLs — if one server is unavailable, the client automatically reconnects to another. Use cluster mode for high availability and horizontal scaling.

NATS client libraries support automatic reconnection with configurable max attempts and backoff intervals. When a connection drops, the client will try to reconnect to any of the configured servers. Subscriptions and pending messages are handled automatically based on QoS settings. Set max reconnect attempts to -1 for infinite retries.

Default NATS client port is 4222. The monitoring HTTP endpoint is on 8222. Cluster routing uses 6222 by default. For TLS, you can use the same 4222 port with TLS configured on the server side, or a dedicated TLS port (common: 4443).