Nats

NATS is a lightweight, high-performance messaging system built for cloud-native architectures: pub/sub for event fan-out, request/reply for RPC patterns, and queue groups for load-balanced work distribution. JetStream (the persistence layer) adds durable streams, consumer state tracking, key-value store, and object storage on top of the core messaging. For agents, NATS is excellent for distributed agent-to-agent messaging, task queue patterns (queue groups), and event sourcing (JetStream streams with replay). Native client libraries (Go, Python, Node.js, Java, Rust, .NET) are preferred over any HTTP wrapper; the protocol is lean and fast. Self-hosted (single binary) or Synadia Cloud/NGS managed. Confidence is docs-derived.

Primary integration via native client libraries, not REST. Core concepts: subjects (named channels), publishers, subscribers, queue groups (competing consumers), JetStream streams (persistent log), consumers (durable or ephemeral). Python: nats-py client (asyncio-native). Node.js: nats.js. Go: nats.go. Connection: nats.connect('nats://host:4222'). Publish: nc.publish('subject', data). Subscribe: nc.subscribe('subject', cb). Request/reply: nc.request('subject', data, timeout). JetStream: js = nc.jetstream(); js.publish('stream.subject', data); consumer = js.subscribe_push('stream', consumer_config). NATS server management via nats CLI tool or nats-server HTTP monitoring endpoint (GET /varz, /subsz, /connz).

NATS supports multiple auth mechanisms: username/password, token-based auth, TLS client certificates, and NKeys (Ed25519 keypairs — the recommended approach). Authorization is subject-based: users can be granted publish/subscribe permissions on specific subject patterns. JetStream operations inherit user permissions. Synadia Cloud uses JWT-based auth with NKeys for multi-tenant isolation. NATS Operators/Accounts model provides strong multi-tenancy for shared deployments. Configuration via server config file or operator JWTs.

NATS server is extremely stable and fast-to-restart. JetStream provides at-least-once delivery; exactly-once available via publish acks and consumer ack tracking. Slow consumer detection: NATS disconnects subscribers that can't keep up (configurable max-pending). Client reconnect logic built into all official SDKs. NATS server health via /healthz endpoint. JetStream persistence to disk or memory. Synadia Cloud SLA. Self-hosted reliability depends on deployment (single node vs. cluster vs. super-cluster). Client SDK retry/reconnect is automatic.

docs.nats.io is comprehensive: covers core concepts, client library guides for all languages, JetStream streams/consumers/KV/object-store, server configuration, security model (NKeys, JWT, TLS), clustering, and Synadia Cloud. Documentation is technically detailed and well-organized. Getting started is easy — single-binary server, client in 3 lines of code. Active CNCF project with strong community (Slack, GitHub). Synadia provides commercial support. NATS CLI tool simplifies operational management.