4 ms·
I can definitely say that RabbitMQ (and the awesome bunny ruby library) is doing the heavy lifting. Batch handling - is actually "prefetch" in RabbitMQ/AMQP. E
by jondot 13y ago
I can definitely say that RabbitMQ (and the awesome bunny ruby library) is doing the heavy lifting.
Batch handling - is actually "prefetch" in RabbitMQ/AMQP. Error reporting - via logging, and a "dead letter mailbox" (called a dead-letter-exchange in RabbitMQ) which is a great enterprise integration pattern for properly handling errors and retries in jobs.
RabbitMQ does the heavy lifting in another surprising facet - the UI. The management UI is excellent and at some point in time I decided not to compete with it by creating my own UI (you have to pick your fights :).
Here's some more info about the management plugin for RabbitMQ.
http://www.rabbitmq.com/management.html http://www.rabbitmq.com/management.html
- bdcravens 13y agoThe thing about Sidekiq is the management is closer to my app, but I'd of course need to look into Rabbit's UI before making any decisions. I suspect that if this project takes off someone will put together a front end that mirrors Sidekiq's in short order.