Seems like a similar design to Apache Kafka, http://kafka.apache.org http://kafka.apache.org. AP, partial ordering (Kafka does ordering within "partitions", but

Seems like a similar design to Apache Kafka, http://kafka.apache.org http://kafka.apache.org. AP, partial ordering (Kafka does ordering within "partitions", but not topics). One difference is that Disque "garbage collects" data once delivery semantics are achieved (client acks) whereas Kafka holds onto all messages within an SLA/TTL, allowing reprocessing. Disque tries to handle at-most-once in the server whereas Kafka leaves it to the client. Will be good to have some fresh ideas in this space, I think. A Redis approach to message queues will be interesting because the speed and client library support is bound to be pretty good.