Hi, I would like to understand the push and pull semantics in nats.io compared to Apache Kafka. The nats_io sub is unfortunately a closed shop. - Source: Reddit / 16 days ago
Funny how the author later worked on NATS [1] which supports exactly-once semantics [2]. -- [1] https://nats.io/ [2] https://docs.nats.io/using-nats/developer/develop_jetstream/model_deep_dive#exactly-once-semantics. - Source: Hacker News / 19 days ago
(G)NATS can do millions of messages per second and is the right tool for the job (either that or NSQ). Redis isn't even the fastest Redis protocol implementation, KeyDB significantly outperforms it. - Source: Reddit / 20 days ago
To anyone not already using Kafka, definitely recommend https://nats.io. - Source: Reddit / 25 days ago
Nice, have you come across NATS? https://nats.io. The server natively supports WebSockets. There are many clients including Deno, Node, WebSockets, Rust, Go, C, Python, etc. In addition to stateless messaging, it supports durable streams, and optimized API layers on top like key-value, and object storage. The server also natively supports MQTT 3.1.1. - Source: Hacker News / about 2 months ago
I feel like you are talking about ‘MQ’ in general term, but you’re describing a pretty specific one. One that is not very flexible and requires you to bend your system around it to make it work. Not all MQs are the same. Some offer a plethora of options to fit your need (ack policy, replay policy, max outstanding, etc) Give NATS a look: https://nats.io/. - Source: Hacker News / 2 months ago
I use JSON-RPC as a standard to command devices that connect to a message bus (I use NATS: https://nats.io/). I wouldn't use it as an alternative to REST or GraphQL, they have different goals/use cases. - Source: Hacker News / 3 months ago
Write a client server chat app using a bus like https://nats.io to communicate between them. It's easy, you can then Dockerise them later and run it via docker-compose. You can even use this to write something similar to https://temp.chat. - Source: Reddit / 4 months ago
Synadia.com — NATS.io as a service. Global, AWS, GCP, and Azure. Free forever with 4k msg size, 50 active connections and 5GB of data per month. - Source: dev.to / 4 months ago
Sounds like a perfect use case for a small footprint, cloud-native queue with gRPC or HTTP protocols and support JSON/Buffer formats. Try to use Memphis or NATS. - Source: Reddit / 5 months ago
> For more details, fenrirproject.org (again: old stuff there, ignore the broken code) Nothing wrong with old stuff, but broken code is going to be a red flag for potential investors. Imho the NATS site (https://nats.io/) is the gold standard for low level project landing pages. Not only does it catch your eye but it gets its point across immediately. You may want to check it out. - Source: Hacker News / 5 months ago
The "shared event bus" could just be nats.io. What you call "server" and "client" would just be clients to nats.io, e.g. One party publishes, the other subscribes and processes the messages. - Source: Reddit / 5 months ago
How does Ziti compare to something like nats (https://nats.io)? - Source: Hacker News / 6 months ago
Exactly once delivery and message ordering is challenging in a distributed system, we can use a dedicated message broker such as Apache Kafka or NATS to make our notification system more robust. - Source: dev.to / 7 months ago
If you are running Kubernetes, or really any kind of microservice architecture, you will eventually run into challenges with communication and synchronization between your instances. To solve this, I recommend deploying an instance of NATS as part of your initial infrastructure setup. NATS is great because:. - Source: dev.to / 6 months ago
For anyone else who didn't understand, it seems OP is talking about NATS.io, which is some edge connectivity project. (This is the first I've ever heard of it.). - Source: Reddit / 6 months ago
Exactly once delivery and message ordering is challenging in a distributed system, we can use a dedicated message broker such as Apache Kafka or NATS to make our notification system more robust. - Source: dev.to / 7 months ago
I've run a load test using SQS with VPC endpoints (to make SQS as close as possible to a service in my VPC) to compare with a Nats based implementation deployed in 3 AZs. - Source: Reddit / 8 months ago
Although it is rough around the edges, I'm using Nasefa daily. This started as learning project. An excuse to play with NATS (https://nats.io). - Source: Hacker News / 9 months ago
Nasefa is a learning project. I could have used existing tools and protocols to do most of what Nasefa does. I decided to implement from scratch mostly to play with NATS. I think this (100% open-source) technology is a game changer for self-hosted, federated and decentralized applications. - Source: Reddit / 9 months ago
Author here. NATS is such an amazing (and underrated) technology in the Go ecosystem and I wanted to talk more about it with some screencasts. Would love your feedback and any suggestions for future screencasts on NATS. - Source: Reddit / 9 months ago
Do you know an article comparing NATS to other products?
Suggest a link to a post with product alternatives.