NATS
No written verdict yet. Here is what commenters said.
Why people recommend it
“NATS and its built-in Jetstream stream persistence engine are a miracle. I love them both so much.”
“one part that always remained up and running without complaining on some dinky machine was NATS”
Show 3 more
“simple binary you can run anywhere and it's highly useful!”
“NATS is far more lightweight, very simple to configure and deploy”
“request reply is really useful if you need low latency, but reasonably efficient queuing”
Caveats and dissent
“generally hesitant to use it in critical systems”
“Given their recentish argument with the CNCF[0] not sure how much I would trust it.”
Show 2 more
“Here is the Jepsen article about Nats”
“The most recent Jepsen analysis again highlights that it's flawed thinking”
Often compared with
Who recommends it in their own words
Threads where it came up
- Jepsen: NATS 2.12.1 9 mentions
- We turned off Pub/Sub and nobody noticed 2 mentions
- Chatto is now Open Source 2 mentions
- What is Apache Kafka and how does it work? 2 mentions
- IBM to acquire Confluent 2 mentions
- Show HN: Pug – open-source product analytics 1 mention
Data: nats.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 27
“built using go, nats, clickhouse, postgres”
“generally hesitant to use it in critical systems”
“Given their recentish argument with the CNCF[0] not sure how much I would trust it.”
“NATS and its built-in Jetstream stream persistence engine are a miracle. I love them both so much.”
“one part that always remained up and running without complaining on some dinky machine was NATS”
“Temporal, Airflow, NATS”
“simple binary you can run anywhere and it's highly useful!”
“I used NATs instead of tmux for agent messaging”
“The whole stack is open source, Kubernetes, Docker, Hashicorp tools, Postgres, Redis, MongoDB, RabbitMQ, NATS, Kafka, Prometheus, Elastic Search, Kibana, Grafana”
“Here is the Jepsen article about Nats”
“NATS is far more lightweight, very simple to configure and deploy”
“Technologies: Rust (Tokio, Axum, Pingora), RocksDB, Python, Kubernetes, AWS/GCP, OpenTelemetry, NATS”
“This project uses Postgres, NATS, Go, Next.js / Typescript”
“The most recent Jepsen analysis again highlights that it's flawed thinking”
“One or two of the comments on GitHub by the NATS team in response to Issues opened by Kyle are also more than a bit cringeworthy.”
“I'm pretty horrified with the report”
“I had given up hope TBH”
“There are many things they don't seem to understand about their own product.”
“the choices it makes for persistence are really surprising”
“it is far more optimistic than what Aphyr uncovered in real-world testing”
https://jepsen.io/analyses/nats-2.12.1
“https://github.com/williamstein/nats-bugs”
> The persistence stuff is kinda new and it's not a surprise that there are limitations and bugs. It's not really that new. The precursor to JetStream was NATS Streaming Server [1], which was first tagged almost 10 years ago [2]. [1] https://github.com/nats-io/nats-streaming-server [2] https://github.com/nats-io/nats-streaming-server/releases/tag/v0.1.0
“request reply is really useful if you need low latency, but reasonably efficient queuing”
“it performed well and was easy to administer”
“Not a drop in replacement, but worth looking at.”
“enterprise-grade distributed orchestration with NATS and CloudEvents”