Live data from Hacker News

NSQ – A realtime distributed messaging platform

nsq.io

61–64 of 64 posts

Re: NSQ – A realtime distributed messaging platform

#62

This looks interesting but I'm hesitant to switch from RabbitMQ & Celery to this.

We use it at Life360, formerly on RabbitMQ. No real issues.

I would also like to know why you made the switch in the first place. Was it the more-easily-distributed nature of nsq?

Re: NSQ – A realtime distributed messaging platform

#63

Earlier quoted context omitted.

Redis pub/sub is ephemeral. If you aren't connected and listening, you missed it.

My mistake: I should have said Redis queues.

NSQ's improvements over Redis queues are:

- NSQ is about equally simple as Redis. Like Redis, it's one binary (and an optional second, if you want a dynamically resizable cluster)

- simplicity of clustering, just boot more servers

- messages aren't lost if the worker process takes one and then dies, they will be retried.

- optional overflow to disk, queues do not have to fit in RAM

- optionally always write to disk, for reliability

- a message on one "channel" can be queued automatically in several "topics", and the sender doesn't need to know. So messages can be diverted to monitoring, for example.

Post reply on HN