You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many requesting clients should be able to access results from the same queue. This is not possible using the redis-queue structure.
The nature of a queue is that each item can only be dequeued (or popped) once. Once an item is dequeued by a client, it is removed from the queue and no longer available for other clients to dequeue.
This proposal should allow multiple clients to subscribe to a consumer group just like using redis streams yet all of them can fetch the result from the enqueued job.
As a worker client, Given #15,
When a job for a queue is alloted for which that worker is assigned,
The worker should store the job_id|worker_id|timestamp into redis,
So that it can:
process that job AND
synchronously fetch results from redis AND
stream it to a redis stream key which is a consumer group.
The text was updated successfully, but these errors were encountered:
codecakes
changed the title
Dynamic Consumer Group subscribers to Queue
Workers can stream results to Consumer Group subscribers for results from a Queue
May 11, 2023
Many requesting clients should be able to access results from the same queue. This is not possible using the redis-queue structure.
The nature of a queue is that each item can only be dequeued (or popped) once. Once an item is dequeued by a client, it is removed from the queue and no longer available for other clients to dequeue.
This proposal should allow multiple clients to subscribe to a consumer group just like using redis streams yet all of them can fetch the result from the enqueued job.
As a worker client, Given #15,
When a job for a queue is alloted for which that worker is assigned,
The worker should store the
job_id|worker_id|timestamp
into redis,So that it can:
The text was updated successfully, but these errors were encountered: