Open jabinb opened 8 years ago
Hello, I wonder what's the difference between the queue tagging approach, and the alternative approach to have just a single queue, named as the tag itself, where the job representation itself states if it's a welcome email, or any other task. The workers just know they need to submit to user_register
and all the related tasks will be delivered to them. Thanks.
A few alternatives:
On Tue, Apr 5, 2016 at 7:12 AM Salvatore Sanfilippo < notifications@github.com> wrote:
Hello, I wonder what's the difference between the queue tagging approach, and the alternative approach to have just a single queue, named as the tag itself, where the job representation itself states if it's a welcome email, or any other task. The workers just know they need to submit to user_register and all the related tasks will be delivered to them. Thanks.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/antirez/disque/issues/130#issuecomment-205758678
Mathieu Longtin 1-514-803-8977
@antirez The problem tagged queues solves is multiple consumers needing the same message but producing different output. A better example would be for an image resizing queue.
Currently I'm achieving this using the first method @mathieulongtin mentions by maintaining my own YAML configuration file of the queues with metadata such as tags/delay.
Hey guys
I'm looking to move from SoftLayers message queue to Disque in the future once a stable release is out. However one of the features that I've found incredibly useful from SL's messaging queue is the ability to tag queues.
For example we have several workflows for when a new user registers (e.g. welcome email, schedule on-boarding drip feed etc). Instead of having to persist somewhere the name of each queue and its role we can simply collect up all the queues with the tag
user_register
and submit the same message to each.This means if we add a new worker that wants to ingest messages relating to that tag (e.g. a feedback email) we just need to add that tag to the queue and then they will receive those messages.
As I understand this would require making queues somewhat persistent as currently they only exist while they contain messages.