queuing

Interesting to hear they were so dissatisfied with Celery/RabbitMQ that chose to write their own queuing system.

It is usually used as cache store, queuing messages to communicate with different processes locally or distributed.

Most of the recent (~10 years?) academic papers on packet queuing algorithms implement their algo in Linux.

Answer: everybody starts queuing up for that ride, even if they don't know which ride it is!

We use queuing systems like RabbitMQ and Kafka to coordinate all this work in progress.

After 9 minutes, shoppers are likely to give up queuing and leave empty handed (other research says as little 6 minutes).

Or anythging like redis, or a queuing system or redundant hardware.

ErlangC assumes queuing, which is probably applicable to this case.

If you have proper layers to handle those things (with queuing/retrying/logging) you end up with a large codebase with very little places where you have to handle exceptions.

Math, particularly statistical analysis, queuing theory, etc.

It will eventually reach an equilibrium with a very high wait time (most specifically, the expected value of the wait time approaches 5 hours as the queuing process continues).

I think it's non-obvious because it quickly gets into queuing theory.

Last I checked, ZeroMQ is more of a "low-level" library/framework that provides easy-paths to more higher-level functionality that would be comparable with what you'd expect from a standard message queuing system.

As the book points out, however, this is a good way to not only burn people out, but it also sends response times through the roof (from queuing theory), and stifles change ("too busy to improve").

Queuing up to send your ebay parcels might be a more current example.

- Databases & Queuing: MongoDB, MySQL, Redis, RabbitMQ, etc.