Disque 1.0 RC1 is out
Disque is definitely exciting, and looks like it can replace RabbitMQ, which has serious flaws in its clustering design. I&#x27;m looking forward to trying it out.<p>However, if some constructive criticism is permitted, I have to say that, having written distributed applications for many years, I have come to dislike the &quot;classical&quot; push&#x2F;pop queue data model:<p>* Acking is a bad idea. It requires the broker to manage a lot of state, including locking and timeouts.<p>* Re-queuing invalidates total ordering.<p>* On the performance side, parallel distributed queue consumption (which also breaks total ordering) is directly at odds with this model.<p>* Queues as opaque objects — you can only inspect by popping the top message, and you cannot access older, dequeued messages. Fortunately, Disque allows you to read the entire queue without mutating it, but it doesn&#x27;t look like you can read old messages.<p>* Complicated queue topologies (fanouts, dead letter queues, etc.) become a logical necessity of the strict FIFO structure. (These topologies need to be declared every time the client starts up, and introduces the possibility of schema conflicts.)<p>* Logical de-duping is probably not possible.<p>Apache Kafka gets the data model right. It wisely acknowledges that queues are linear and should stay that way: In Kafka, queues are strictly append-only logs where every consumer has a cursor to the last position it read. In this model, many of the classical concerns melt away: Acks&#x2F;nacks are unnecessary (consumers simply &quot;commit&quot; their position); total ordering is always preserved (since the queue cannot be reordered) and parallelism is made explicit (through named partitions); de-duping is trivial, and complicated topologies are largely eliminated (AMQP-type &quot;exchanges&quot; that fan out to separate queues are unnecessary because multiple readers can all consume the same queue without changing it, as their position is independent of the queue); and you get to choose either at-most-once or at-least-once delivery consistency by how carefully you manage your offset.<p>Since logs are strictly linear, you are also given the choice of how much history to keep — all of it, if you want — which opens up some interesting use cases that are not possible with classical brokers.<p>Kafka isn&#x27;t perfect. It&#x27;s a huge pain if you&#x27;re not in Java land. There are no modern, mature &quot;high-level&quot; client implementations for Go, Ruby or Node.js. Its reliance on the JVM and on ZooKeeper makes it fairly heavyweight, both on the server and on the consumer side (the new API for broker-stored offsets simplifies things, but non-Java clients are far behind). I would really love to have a lighter-weight, language-agnostic Kafka-like implementation without the Java baggage.<p>Last point: The fact that Disque calls its messages &quot;jobs&quot; makes me a little disappointed that it is, in fact, not a job management system. I&#x27;d love a solid, distributed job manager.