{"slug": "nats", "name": "NATS", "category": "communication", "category_name": "Email and chat", "description": "", "recommenders": 6, "commenters": 24, "warners": 10, "score": -1.666, "rising": -1.96, "first": "2025-11-16", "latest": "2026-10-20", "why": "NATS and its built-in Jetstream stream persistence engine are a miracle. I love them both so much.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 6, "neutral": 9, "compare": 0, "warn": 10}, "spark": [0, 2, 0, 0, 0, 0, 2, 0, 2, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "NATS and its built-in Jetstream stream persistence engine are a miracle. I love them both so much.", "kind": "", "icon": true, "domain": "nats.io", "github_repo": null, "official_url": "https://nats.io", "pricing": "", "aliases": ["NATS"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 781490640, "item_id": 48843165, "url": "https://news.ycombinator.com/item?id=48843165", "by": "hendrikmans", "date": "2026-07-09", "version": null, "stance": "recommend", "quote": "NATS and its built-in Jetstream stream persistence engine are a miracle. I love them both so much.", "excerpt": "Hi, Chatto developer here. NATS and its built-in Jetstream stream persistence engine are a miracle. I love them both so much. And if your app is itself written in Go, you can just embed them for simple deployment scenarios (like Chatto does.)", "context": "Chatto developer", "use_case": "messaging and persistence", "switched_from": "", "story": "Chatto is now Open Source"}, {"id": 781431424, "item_id": 48839464, "url": "https://news.ycombinator.com/item?id=48839464", "by": "lofties", "date": "2026-07-08", "version": null, "stance": "recommend", "quote": "one part that always remained up and running without complaining on some dinky machine was NATS", "excerpt": "Wow, it's using NATS! I used NATS extensively 10+ years ago, and I'm happy to hear it's still around. Our infrastructure had hiccups across our fleet of machines, but one part that always remained up and running without complaining on some dinky machine was NATS. Well, that and Redis. No complaints ever.", "context": "used it extensively 10+ years ago", "use_case": "message broker across fleet", "switched_from": "", "story": "Chatto is now Open Source"}, {"id": 773537008, "item_id": 48346063, "url": "https://news.ycombinator.com/item?id=48346063", "by": "fjwood69", "date": "2026-05-31", "version": null, "stance": "recommend", "quote": "simple binary you can run anywhere and it's highly useful!", "excerpt": "So I solved this by using NATS and letting each agent pub / sub to the shared message bus.. simple binary you can run anywhere and it's highly useful! Part of a broader tool I created - https://github.com/fjwood69/mori", "context": "", "use_case": "", "switched_from": "", "story": "Claude Code and Codex Can Have Real-Time Conversation via Git"}, {"id": 767801616, "item_id": 47987601, "url": "https://news.ycombinator.com/item?id=47987601", "by": "sudonem", "date": "2026-05-02", "version": null, "stance": "recommend", "quote": "NATS is far more lightweight, very simple to configure and deploy", "excerpt": "There\u2019s obviously no single solution, it won\u2019t make sense for all use cases, but NATS is far more lightweight, very simple to configure and deploy, has very few dependencies and offers incredibly low latency. NATS with Jetstream also closes the gap even further. Kafka still wins for very large data pipelines (hundreds of terabytes or petabytes), complex stream processing, or very long retention requirements for messa", "context": "", "use_case": "Lightweight messaging", "switched_from": "", "story": "What is Apache Kafka and how does it work?"}, {"id": 739163936, "item_id": 46197746, "url": "https://news.ycombinator.com/item?id=46197746", "by": "KaiserPro", "date": "2025-12-08", "version": null, "stance": "recommend", "quote": "request reply is really useful if you need low latency, but reasonably efficient queuing", "excerpt": "MQTT doesn't have the same semantics. https://docs.nats.io/nats-concepts/core-nats/reqreply request reply is really useful if you need low latency, but reasonably efficient queuing. (making sure to mark your workers as busy when processing otherwise you get latency spikes. )", "context": "", "use_case": "request-reply messaging", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 789753424, "item_id": 49359589, "url": "https://news.ycombinator.com/item?id=49359589", "by": "DavyJone", "date": "2026-08-19", "version": null, "stance": "warn", "quote": "generally hesitant to use it in critical systems", "excerpt": "I really like NATS and I agree, but im generally hesitant to use it in critical systems due to https://jepsen.io/analyses/nats-2.12.1 What is your take on this?", "context": "", "use_case": "", "switched_from": "", "story": "We turned off Pub/Sub and nobody noticed"}, {"id": 788569264, "item_id": 49285579, "url": "https://news.ycombinator.com/item?id=49285579", "by": "jdon", "date": "2026-08-13", "version": null, "stance": "warn", "quote": "Given their recentish argument with the CNCF[0] not sure how much I would trust it.", "excerpt": "Given their recentish argument with the CNCF[0] not sure how much I would trust it. [0] https://www.cncf.io/blog/2025/05/01/protecting-nats-and-the-integrity-of-open-source-cncfs-commitment-to-the-community/", "context": "", "use_case": "", "switched_from": "", "story": "We turned off Pub/Sub and nobody noticed"}, {"id": 767850352, "item_id": 47990647, "url": "https://news.ycombinator.com/item?id=47990647", "by": "0xcoffee", "date": "2026-05-02", "version": null, "stance": "warn", "quote": "Here is the Jepsen article about Nats", "excerpt": "Here is the Jepsen article about Nats: https://jepsen.io/analyses/nats-2.12.1", "context": "", "use_case": "", "switched_from": "", "story": "What is Apache Kafka and how does it work?"}, {"id": 741374720, "item_id": 46335920, "url": "https://news.ycombinator.com/item?id=46335920", "by": "formerly_proven", "date": "2025-12-20", "version": null, "stance": "warn", "quote": "The most recent Jepsen analysis again highlights that it's flawed thinking", "excerpt": "But we know this is not actually robust because storage and power failures tend to be correlated. The most recent Jepsen analysis again highlights that it's flawed thinking: https://jepsen.io/analyses/nats-2.12.1", "context": "", "use_case": "", "switched_from": "", "story": "What Does a Database for SSDs Look Like?"}]}], "who": [{"by": "hendrikmans", "context": "Chatto developer", "url": "https://news.ycombinator.com/item?id=48843165", "date": "2026-07-09"}, {"by": "lofties", "context": "used it extensively 10+ years ago", "url": "https://news.ycombinator.com/item?id=48839464", "date": "2026-07-08"}, {"by": "graerg", "context": "Senior Data Science Manager at Hyundai Motor America; job seeker", "url": "https://news.ycombinator.com/item?id=48750378", "date": "2026-07-01"}, {"by": "DeathArrow", "context": "C# microservices developer, 6 years", "url": "https://news.ycombinator.com/item?id=48106708", "date": "2026-05-12"}, {"by": "abhirag", "context": "Systems engineer", "url": "https://news.ycombinator.com/item?id=47981448", "date": "2026-05-01"}], "tags": [], "use_cases": ["messaging", "messaging and persistence", "message broker across fleet", "agent messaging", "lightweight messaging", "messaging for workloads"], "compared": [{"slug": "redis", "name": "Redis", "co": 4, "switched_from": 0, "switched_to": 0}, {"slug": "postgresql", "name": "PostgreSQL", "co": 4, "switched_from": 0, "switched_to": 0}, {"slug": "sqlite", "name": "SQLite", "co": 1, "switched_from": 0, "switched_to": 1}, {"slug": "kubernetes", "name": "Kubernetes", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "apache-kafka", "name": "Apache Kafka", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "tmux", "name": "tmux", "co": 1, "switched_from": 1, "switched_to": 0}, {"slug": "rabbitmq", "name": "RabbitMQ", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=46196105", "title": "Jepsen: NATS 2.12.1", "mentions": 9}, {"url": "https://news.ycombinator.com/item?id=49285325", "title": "We turned off Pub/Sub and nobody noticed", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=48833116", "title": "Chatto is now Open Source", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=47984411", "title": "What is Apache Kafka and how does it work?", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=46192130", "title": "IBM to acquire Confluent", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=50166960", "title": "Show HN: Pug \u2013 open-source product analytics", "mentions": 1}], "sentiment_by_month": {"2025-11": {"neutral": 1}, "2025-12": {"recommend": 2, "neutral": 2, "warn": 7}, "2026-01": {"neutral": 1}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {"neutral": 3, "recommend": 2, "warn": 1}, "2026-06": {}, "2026-07": {"neutral": 1, "recommend": 2}, "2026-08": {"warn": 2}, "2026-09": {}, "2026-10": {"neutral": 1}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 802677571, "item_id": 50167348, "url": "https://news.ycombinator.com/item?id=50167348", "by": "BajajScooter", "date": "2026-10-20", "version": null, "stance": "neutral", "quote": "built using go, nats, clickhouse, postgres", "excerpt": "built using go, nats, clickhouse, postgres; goal is to make it easy to self host github: https://github.com/pug-sh/pug demo(no sign up needed): https://app.pug.sh/demo", "context": "", "use_case": "messaging", "switched_from": "", "story": "Show HN: Pug \u2013 open-source product analytics"}, {"id": 789753424, "item_id": 49359589, "url": "https://news.ycombinator.com/item?id=49359589", "by": "DavyJone", "date": "2026-08-19", "version": null, "stance": "warn", "quote": "generally hesitant to use it in critical systems", "excerpt": "I really like NATS and I agree, but im generally hesitant to use it in critical systems due to https://jepsen.io/analyses/nats-2.12.1 What is your take on this?", "context": "", "use_case": "", "switched_from": "", "story": "We turned off Pub/Sub and nobody noticed"}, {"id": 788569264, "item_id": 49285579, "url": "https://news.ycombinator.com/item?id=49285579", "by": "jdon", "date": "2026-08-13", "version": null, "stance": "warn", "quote": "Given their recentish argument with the CNCF[0] not sure how much I would trust it.", "excerpt": "Given their recentish argument with the CNCF[0] not sure how much I would trust it. [0] https://www.cncf.io/blog/2025/05/01/protecting-nats-and-the-integrity-of-open-source-cncfs-commitment-to-the-community/", "context": "", "use_case": "", "switched_from": "", "story": "We turned off Pub/Sub and nobody noticed"}, {"id": 781490640, "item_id": 48843165, "url": "https://news.ycombinator.com/item?id=48843165", "by": "hendrikmans", "date": "2026-07-09", "version": null, "stance": "recommend", "quote": "NATS and its built-in Jetstream stream persistence engine are a miracle. I love them both so much.", "excerpt": "Hi, Chatto developer here. NATS and its built-in Jetstream stream persistence engine are a miracle. I love them both so much. And if your app is itself written in Go, you can just embed them for simple deployment scenarios (like Chatto does.)", "context": "Chatto developer", "use_case": "messaging and persistence", "switched_from": "", "story": "Chatto is now Open Source"}, {"id": 781431424, "item_id": 48839464, "url": "https://news.ycombinator.com/item?id=48839464", "by": "lofties", "date": "2026-07-08", "version": null, "stance": "recommend", "quote": "one part that always remained up and running without complaining on some dinky machine was NATS", "excerpt": "Wow, it's using NATS! I used NATS extensively 10+ years ago, and I'm happy to hear it's still around. Our infrastructure had hiccups across our fleet of machines, but one part that always remained up and running without complaining on some dinky machine was NATS. Well, that and Redis. No complaints ever.", "context": "used it extensively 10+ years ago", "use_case": "message broker across fleet", "switched_from": "", "story": "Chatto is now Open Source"}, {"id": 780006061, "item_id": 48750378, "url": "https://news.ycombinator.com/item?id=48750378", "by": "graerg", "date": "2026-07-01", "version": null, "stance": "neutral", "quote": "Temporal, Airflow, NATS", "excerpt": "Location: Orange County, CA (Pacific Time) Remote: Yes (preferred); hybrid Orange County also fine Willing to relocate: No Technologies: Python, Go, SQL | FastAPI, Django, Vue, HTMX | Postgres, TimescaleDB, DuckDB, Redis | Temporal, Airflow, NATS | AWS (S3/RDS/EC2/Redshift), Docker, Kubernetes | Prometheus/Grafana | LLMs in production (RAG, eval, orchestration, structured extraction) Resume/CV: https://brojonat.com/J", "context": "Senior Data Science Manager at Hyundai Motor America; job seeker", "use_case": "", "switched_from": "", "story": "Ask HN: Who wants to be hired? (July 2026)"}, {"id": 773537008, "item_id": 48346063, "url": "https://news.ycombinator.com/item?id=48346063", "by": "fjwood69", "date": "2026-05-31", "version": null, "stance": "recommend", "quote": "simple binary you can run anywhere and it's highly useful!", "excerpt": "So I solved this by using NATS and letting each agent pub / sub to the shared message bus.. simple binary you can run anywhere and it's highly useful! Part of a broader tool I created - https://github.com/fjwood69/mori", "context": "", "use_case": "", "switched_from": "", "story": "Claude Code and Codex Can Have Real-Time Conversation via Git"}, {"id": 770721350, "item_id": 48170084, "url": "https://news.ycombinator.com/item?id=48170084", "by": "apiemotion", "date": "2026-05-17", "version": null, "stance": "neutral", "quote": "I used NATs instead of tmux for agent messaging", "excerpt": "Confession: all vibe engineered using OpenCode, Gemini & Cursor. I started by wanting to try GasTown without needing a Claude Subscription. Freeride proxy was developed to use free Cloud hosted models. It started with NVIDIA NIM then I added OpenRouter. Now it also support Cerebras and Ollama Cloud. It manages fallbacks & cool downs. I recently added a local LLM if it is capable. There is flag to spend money if one w", "context": "", "use_case": "agent messaging", "switched_from": "tmux", "story": "I want to try S.Y's GasTown to create code from a Spec without spending any $"}, {"id": 769707334, "item_id": 48106708, "url": "https://news.ycombinator.com/item?id=48106708", "by": "DeathArrow", "date": "2026-05-12", "version": null, "stance": "neutral", "quote": "The whole stack is open source, Kubernetes, Docker, Hashicorp tools, Postgres, Redis, MongoDB, RabbitMQ, NATS, Kafka, Prometheus, Elastic Search, Kibana, Grafana", "excerpt": "Hmm, I am working on C# microservices based apps since 6 years ago. And I always deployed on cloud using Linux, usually in Kubernetes. I used Google Cloud and AWS beside Azure. The whole stack is open source, Kubernetes, Docker, Hashicorp tools, Postgres, Redis, MongoDB, RabbitMQ, NATS, Kafka, Prometheus, Elastic Search, Kibana, Grafana and so on and so forth.", "context": "C# microservices developer, 6 years", "use_case": "", "switched_from": "", "story": "If AI Writes Your Code, Why Use Python?"}, {"id": 767850352, "item_id": 47990647, "url": "https://news.ycombinator.com/item?id=47990647", "by": "0xcoffee", "date": "2026-05-02", "version": null, "stance": "warn", "quote": "Here is the Jepsen article about Nats", "excerpt": "Here is the Jepsen article about Nats: https://jepsen.io/analyses/nats-2.12.1", "context": "", "use_case": "", "switched_from": "", "story": "What is Apache Kafka and how does it work?"}, {"id": 767801616, "item_id": 47987601, "url": "https://news.ycombinator.com/item?id=47987601", "by": "sudonem", "date": "2026-05-02", "version": null, "stance": "recommend", "quote": "NATS is far more lightweight, very simple to configure and deploy", "excerpt": "There\u2019s obviously no single solution, it won\u2019t make sense for all use cases, but NATS is far more lightweight, very simple to configure and deploy, has very few dependencies and offers incredibly low latency. NATS with Jetstream also closes the gap even further. Kafka still wins for very large data pipelines (hundreds of terabytes or petabytes), complex stream processing, or very long retention requirements for messa", "context": "", "use_case": "Lightweight messaging", "switched_from": "", "story": "What is Apache Kafka and how does it work?"}, {"id": 767703176, "item_id": 47981448, "url": "https://news.ycombinator.com/item?id=47981448", "by": "abhirag", "date": "2026-05-01", "version": null, "stance": "neutral", "quote": "Technologies: Rust (Tokio, Axum, Pingora), RocksDB, Python, Kubernetes, AWS/GCP, OpenTelemetry, NATS", "excerpt": "Location: Bangalore, India Remote: Yes Willing to relocate: Yes Technologies: Rust (Tokio, Axum, Pingora), RocksDB, Python, Kubernetes, AWS/GCP, OpenTelemetry, NATS R\u00e9sum\u00e9/CV: https://abhirag.com/resume.pdf Email: hey@abhirag.com Systems engineer, ~5 years of Rust in production. Most recently: - Helped build a distributed notification engine (3.3B notifications/day at 300k/sec, 99.9999% dispatch reliability) - Featur", "context": "Systems engineer", "use_case": "", "switched_from": "", "story": "Ask HN: Who wants to be hired? (May 2026)"}, {"id": 745268018, "item_id": 46579251, "url": "https://news.ycombinator.com/item?id=46579251", "by": "osigurdson", "date": "2026-01-11", "version": null, "stance": "neutral", "quote": "This project uses Postgres, NATS, Go, Next.js / Typescript", "excerpt": "I built a system to ingest data and \"do AI stuff with it\". I think it is kind of useful. Here is an example from this post: https://nthesis.ai/public/hn-working-on (updates live). I think my UI is kind of bad as no one seems to realize you can chat with the data as well (try the chat button). I've done quite a bit with auto-curation so you can ask questions like \"What are the general themes in the posts this month?\" ", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: What Are You Working On? (January 2026)"}, {"id": 741374720, "item_id": 46335920, "url": "https://news.ycombinator.com/item?id=46335920", "by": "formerly_proven", "date": "2025-12-20", "version": null, "stance": "warn", "quote": "The most recent Jepsen analysis again highlights that it's flawed thinking", "excerpt": "But we know this is not actually robust because storage and power failures tend to be correlated. The most recent Jepsen analysis again highlights that it's flawed thinking: https://jepsen.io/analyses/nats-2.12.1", "context": "", "use_case": "", "switched_from": "", "story": "What Does a Database for SSDs Look Like?"}, {"id": 739269104, "item_id": 46204319, "url": "https://news.ycombinator.com/item?id=46204319", "by": "traceroute66", "date": "2025-12-09", "version": null, "stance": "warn", "quote": "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.", "excerpt": "> Nominate NATS for the Silent Failure Peace Prize? 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. Such as this one: \"Most of our production setups, and in fact Synadia Cloud as well is that each replica is in a separate AZ. These have separate power, networking etc. So the possibility of a loss here is extremely low in terms of due to", "context": "", "use_case": "", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}, {"id": 739248640, "item_id": 46203040, "url": "https://news.ycombinator.com/item?id=46203040", "by": "ownagefool", "date": "2025-12-09", "version": null, "stance": "warn", "quote": "I'm pretty horrified with the report", "excerpt": "I suspect they were more referring to curmudgeons not patching. I was engaged after one of the worlds biggest data leaks. The Security org was hyper worried about the cloud environment, which was in its infancy, despite the fact their data leak was from on-prem mainframe style system and they hadn't really improved their posture in any significant way despite spending \u00a340m. As an aside, I use NATs for some workloads ", "context": "", "use_case": "Messaging for workloads", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}, {"id": 739245728, "item_id": 46202858, "url": "https://news.ycombinator.com/item?id=46202858", "by": "jessekv", "date": "2025-12-09", "version": null, "stance": "warn", "quote": "I had given up hope TBH", "excerpt": "A tiny bit more context here: https://github.com/nats-io/nats-server/discussions/3312#discussioncomment-15203259 (I opened this discussion 2.5 years ago and get an email from github every once in a while ever since. I had given up hope TBH)", "context": "", "use_case": "", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}, {"id": 739242224, "item_id": 46202639, "url": "https://news.ycombinator.com/item?id=46202639", "by": "PaoloBarbolini", "date": "2025-12-09", "version": null, "stance": "warn", "quote": "There are many things they don't seem to understand about their own product.", "excerpt": "There are many things they don't seem to understand about their own product. https://github.com/nats-io/nats.rs/issues/1253#issuecomment-2063047468", "context": "", "use_case": "", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}, {"id": 739237024, "item_id": 46202314, "url": "https://news.ycombinator.com/item?id=46202314", "by": "williamstein", "date": "2025-12-08", "version": null, "stance": "warn", "quote": "the choices it makes for persistence are really surprising", "excerpt": "For example, https://github.com/williamstein/nats-bugs/issues/5 links to a discussion I have with them about data loss, where they fundamentally don't understand that their incorrect defaults lead to data loss on the application side. It's weird. I got very deep into using NATS last year, and then realized the choices it makes for persistence are really surprising. Another horrible example if that server startup time", "context": "", "use_case": "", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}, {"id": 739236817, "item_id": 46202301, "url": "https://news.ycombinator.com/item?id=46202301", "by": "PeterCorless", "date": "2025-12-08", "version": null, "stance": "warn", "quote": "it is far more optimistic than what Aphyr uncovered in real-world testing", "excerpt": "You can have DeepWiki literally scan the source code and tell you: > 2. Delayed Sync Mode (Default) > In the default mode, writes are batched and marked with needSync = true for later synchronization filestore.go:7093-7097 . The actual sync happens during the next syncBlocks() execution. However, if you read DeepWiki's conclusion, it is far more optimistic than what Aphyr uncovered in real-world testing. > Durability", "context": "", "use_case": "", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}, {"id": 739228320, "item_id": 46201770, "url": "https://news.ycombinator.com/item?id=46201770", "by": "shadow28", "date": "2025-12-08", "version": null, "stance": "neutral", "quote": "", "excerpt": "https://jepsen.io/analyses/nats-2.12.1", "context": "", "use_case": "", "switched_from": "", "story": "IBM to acquire Confluent"}, {"id": 739178016, "item_id": 46198626, "url": "https://news.ycombinator.com/item?id=46198626", "by": "williamstein", "date": "2025-12-08", "version": null, "stance": "warn", "quote": "https://github.com/williamstein/nats-bugs", "excerpt": "https://github.com/williamstein/nats-bugs", "context": "", "use_case": "", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}, {"id": 739173552, "item_id": 46198347, "url": "https://news.ycombinator.com/item?id=46198347", "by": "njuw", "date": "2025-12-08", "version": null, "stance": "neutral", "quote": "", "excerpt": "> 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", "context": "", "use_case": "", "switched_from": "", "story": null}, {"id": 739163936, "item_id": 46197746, "url": "https://news.ycombinator.com/item?id=46197746", "by": "KaiserPro", "date": "2025-12-08", "version": null, "stance": "recommend", "quote": "request reply is really useful if you need low latency, but reasonably efficient queuing", "excerpt": "MQTT doesn't have the same semantics. https://docs.nats.io/nats-concepts/core-nats/reqreply request reply is really useful if you need low latency, but reasonably efficient queuing. (making sure to mark your workers as busy when processing otherwise you get latency spikes. )", "context": "", "use_case": "request-reply messaging", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}, {"id": 739161888, "item_id": 46197618, "url": "https://news.ycombinator.com/item?id=46197618", "by": "KaiserPro", "date": "2025-12-08", "version": null, "stance": "recommend", "quote": "it performed well and was easy to administer", "excerpt": "NATS is very upfront in that the only thing that is guaranteed is the cluster being up. I like that, and it allows me to build things around it. For us when we used it back in 2018, it performed well and was easy to administer. The multi-language APIs were also good.", "context": "", "use_case": "", "switched_from": "", "story": "Jepsen: NATS 2.12.1"}, {"id": 739087504, "item_id": 46192969, "url": "https://news.ycombinator.com/item?id=46192969", "by": "osigurdson", "date": "2025-12-08", "version": null, "stance": "recommend", "quote": "Not a drop in replacement, but worth looking at.", "excerpt": "https://nats.io Not a drop in replacement, but worth looking at.", "context": "", "use_case": "", "switched_from": "", "story": "IBM to acquire Confluent"}, {"id": 735106434, "item_id": 45944152, "url": "https://news.ycombinator.com/item?id=45944152", "by": "haai007", "date": "2025-11-16", "version": null, "stance": "neutral", "quote": "enterprise-grade distributed orchestration with NATS and CloudEvents", "excerpt": "I built Farmland because I was tired of complex Jenkinsfile setups or explaining dependency graphs to my CEO. The insight: Everyone understands farm operations. You plant before you harvest. Different crops need different care. These same principles apply to software builds, but current tools hide this natural logic. As it is with testing, you should test one thing not many, setup test teardown. Same is with pipeline", "context": "", "use_case": "", "switched_from": "", "story": null}]}