4 ms·
This caught my eye as well, because the article talks about how big a pain it is to set up & maintain queuing servers, but then provides a solution that simply
by arscan 14y ago
This caught my eye as well, because the article talks about how big a pain it is to set up & maintain queuing servers, but then provides a solution that simply isn't as robust.
But to be honest, the fact that they open sourced all these libraries and present them front-and-center for anybody interested makes up for that. There isn't any magic going on -- just some straightforward code that leverages language/runtime-appropriate mechanisms to queue up the messages. Its pretty easy to figure out if the solution meets your performance needs when you can see the actual code being run.
- bigiain 14y agoSure, its not as robust as a generalised queuing system, but it's web analytics - the driving reason for queuing is more about high performance than about guaranteed message delivery. Lightweight and _fast_ in-memory queues seem like a perfectly adequate solution fr the problem domain, while being (as claimed) significantly less of a pain to set up than "traditional" queuing techniques.