This is a good case-study of what to do when building a home page for your project.<p>1) State what your project is about using language that a reasonably savvy (technology-wise) user can understand, even if unfamiliar with the problem domain. (this site would be better if they linked on "message queue" for those people that don't know what that is.)<p>2) Eye-catching call to action icons<p>3) Brief list of most important features<p>4) Brief high-level view<p>5) Brief low-level view<p>6) Some clean and minimalist stats on why you might want to use it<p>7) Easy to understand links to more info.<p>I don't know if I will ever need this product... but I'm bookmarking it anyway as an <i>outstanding</i> example of how to introduce people to it. (Except for the swear word. The word "Fucking" is really out of place)<p>Nice job guys.
The throughput numbers on the chart would have seemed a bit more valid if the task had not included stuffing the result into a protobuf given the notoriously slow performance of the standard python protobuf implementation that would have been used by Celery and PyInvoke. If they wanted to impress, or at least be honest, the data would have stayed in JSON the whole way through the stack and the worker task would have been a simple string manipulation of something similar.
Am I the only one who got really excited upon seeing the domain was octobot.taco.cat, and then very confused when going to www.taco.cat? It seems to be an art gallery in Spanish or something...<p>I realize this is not germane to the topic, but .cat!? What other really interesting tld's exist that I have never heard about?
Fascinating. The thing I find interesting about this service is that it seems to work seamlessly with multiple queue backends. That would have been really useful at my company, where we completely swapped out our queue server infrastructure. Nice work!
Interesting; I'm looking forward to comparing/contrasting this with my current favorite - Celery (<a href="http://celeryproject.org/" rel="nofollow">http://celeryproject.org/</a>) which supports a variety of backends.
I like that it has the capability to be an email queue build in, by supporting SMTP/SSL. Worth installing just for that, since that's the first thing lots of websites want a message queue for.
Very interesting. We're currently working on a quick project to test integrating Hazelcast into a distributed server to use as a queue. Did you look at it by any chance? Curious if it was missing something that you needed.
Interesting, but won't ever use. It also seems that it is just wrapping typical queueing systems, which I would use anyways because this only supports the JVM.