4 ms·
We debated the same question and went with NSQ for now. We might need some of the guarantees that Kafka makes in the longterm or for some specific use cases, bu
by be_erik 9y ago
We debated the same question and went with NSQ for now. We might need some of the guarantees that Kafka makes in the longterm or for some specific use cases, but for a no thrills distributed messaging platform that is incredibly simple to operate at scale, NSQ is pretty fantastic.
Building client libraries is also a joy. I blogged about it a bit here: https://product.reverb.com/how-to-write-an-nsq-consumer-in-go-96ed8bde29ef https://product.reverb.com/how-to-write-an-nsq-consumer-in-g...
- rafaeljesus 9y agoNice one! Just as a info, I wrapped producer/consumer in a pkg https://github.com/rafaeljesus/nsq-event-bus https://github.com/rafaeljesus/nsq-event-bus also it exposes request-reply/rpc like