Nats Rate Limits
NATS open source does not enforce request-per-second rate limits via HTTP — it is a TCP/WebSocket messaging server. Operator-enforced limits are configured per Account via JWT claims (max connections, max subscriptions, max payload, max data, max leaf nodes). The HTTP monitoring endpoints on port 8222 are unauthenticated and intended for operations dashboards. Synadia Cloud, the managed offering, enforces per-Team quotas defined by subscription tier (connections, subscriptions, network data, storage, message size) rather than RPS throttling.
Nats Rate Limits is the machine-readable rate-limit profile for NATS on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 8 rate-limit definitions, measuring concurrent_connections, concurrent_subscriptions, bytes_per_message, and bytes.
The profile also includes 4 backoff/retry policies defined and response codes documented for quotaExceeded.
Tagged areas include Rate Limiting, Message Broker, Pub Sub, and Streaming.