4 ms·
I don't think I had heard about NSQ till now; how is it better than, say, a pub-sub queue on a beefy Redis server? (Or a cluster of servers, if you wish). Noth
by discardorama 12y ago
I don't think I had heard about NSQ till now; how is it better than, say, a pub-sub queue on a beefy Redis server? (Or a cluster of servers, if you wish). Nothing beats Redis' simplicity, AFAICT.
- JulianMorrison 12y agoRedis pub/sub is ephemeral. If you aren't connected and listening, you missed it.
- discardorama 12y agoMy mistake: I should have said Redis queues.
- JulianMorrison 12y agoNSQ'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.