Re:Disque 1.0 RC1 is out
by vdfs on Saturday January 02, 2016 @01:37PM
(#10827224)
Is there a product-ready alternative to Disque?
[ Parent
| on HN ]
There are plenty, but few/none that solve the problem Disque solves. You could easily use Kafka or RabbitMQ, but Disque aims to provide simplicity rather than be full-featured. @antirez described it as solving the case where you just need a queue with very basic guarantees and good performance without all the bells and whistles that a more complex system has. Disque is (spiritually, not technically) a lot like Mongo was five years ago compared to something much heavier like Postgres. In that sense, there are few (if any) product-ready alternatives that solve the same problem.
It should also be noted that you could probably successfully use Redis for much of what Disque does (Disque is based on Redis). Disque adds nice features, though, and removes most of the features of Redis that are outside its scope.
I've been using Sidekiq for the past 2 years, and deem it as production ready. It does force you to use Redis and Ruby though.
I'd guess Sidekiq could be adapted to work with Disque too (as Disque takes off).
I'm building a node.js application now and WISH we had something half as good as Sidekiq written in Javascript.
You can use Sidekiq in many environments where somebody has written libraries, eg. Go, Elixir, JavaScript (https://github.com/loopj/node-sidekiq) .
Re:Disque 1.0 RC1 is out
by true_religion on Saturday January 02, 2016 @04:50PM
(#10828136)
How would you say it compares to something like Celery?
I found sidekiq to be better than celery for my needs because it was better integrated (although less configurable). It did what it said on the box without a fuss and without me having to debate the merits of and choose a backend, etc...
It worked with redis and it worked well.
We have used nsq to ship billions of log messages daily for over 2 years. It is very sensible operationly and easy to configure to the level of robustness your use may have. It does not allow seeking into the queue like Kafka, but we have never needed that capability, and we found it easier to design around this rather than take on the operational burden.
Re:Disque 1.0 RC1 is out
by BradRuderman on Saturday January 02, 2016 @02:23PM
(#10827466)
It seems like Disque is a "simplified" Kafka, or a more vertically purposed Redis. It seems that it differs from RabbitMQ significantly because rabbit requires a queue to push the messages in, while Disque allows jobs to be pushed independently of consumers being setup.
Re:Disque 1.0 RC1 is out
by lobster_johnson on Saturday January 02, 2016 @05:47PM
(#10828374)
Kafka is arguably simpler, at least in terms of data model, than Disque. Disque needs to handle acking and queue mutation and things like lock timeouts and dead lettering, all of which complicates its queue structure and API. Kafka queues (partitions, to be precise) are append-only, which simplifies a lot of things.