NSQ Reviews and details

Social recommendations and mentions

• Any thoughts on using Redis to extend Go's channels across application / machine boundaries?

  (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: about 1 year ago

• FileWave: Why we moved from ZeroMQ to NATS

  Bit.ly's NSQ is also an excellent message queue option. Source: about 1 year ago

• Infinite loop pattern to poll for a queue in a REST server app

  Queue consumers are interesting because there are many solutions for them, from using Redis and persisting the data in a data store - but for fast and scalable the approach I would take is something like SQS (as I advocate AWS even free tier) or NSQ for managing your own distributed producers and consumers. Source: over 1 year ago

• What are pros and cons of Go?

  Distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on). Source: almost 2 years ago

• Distributed IM Service in Golang

  NSQ is a message queue implemented by Golang, and all messages are routed through NSQ. Reasons for choosing NSQ compared to other MQs: decentralized distribution (direct connection between production and consumption), low latency, No ordering, high performance, simple binary protocol. - Source: dev.to / almost 2 years ago

• Fluvio: The Programmable Data Platform

  If we are talking about "cloud-native", I would really recommend taking a look at nsq or nats. I am really big fanboy of NSQ [1], it is simple, easy to setup and conceptually easy to learn. [1] https://nsq.io. - Source: Hacker News / almost 3 years ago

• For those running Go in production at scale, what do you use for distributed task queues?

  I've been using NSQ in production for a number of years now. It's also written in Go and has a first class client library maintained by the devs. Source: almost 3 years ago