[GH-ISSUE #241] [FEATURE REQUEST] Redis key prefix #85

Closed
opened 2026-03-02 05:18:32 +03:00 by kerem · 5 comments
Owner

Originally created by @hellish on GitHub (Feb 6, 2021).
Original GitHub issue: https://github.com/hibiken/asynq/issues/241

Originally assigned to: @hibiken on GitHub.

Is your feature request related to a problem? Please describe.
no

Describe the solution you'd like
I want to be able to specify a prefix for all redis keys and pub sub channels used in this library. right now everything resides in asynq.* namespace but with a prefix it will be myapp.asynq.*

Originally created by @hellish on GitHub (Feb 6, 2021). Original GitHub issue: https://github.com/hibiken/asynq/issues/241 Originally assigned to: @hibiken on GitHub. **Is your feature request related to a problem? Please describe.** no **Describe the solution you'd like** I want to be able to specify a prefix for all redis keys and pub sub channels used in this library. right now everything resides in asynq.* namespace but with a prefix it will be myapp.asynq.*
kerem 2026-03-02 05:18:32 +03:00
Author
Owner

@hibiken commented on GitHub (Feb 7, 2021):

@hellish Thank you for opening this issue!
Would you mind explaining the reason you need this feature in detail, so that I can understand the use case.
It shouldn't be too difficult to add this feature, but I'm not 100% convinced that we need to support this.

<!-- gh-comment-id:774575814 --> @hibiken commented on GitHub (Feb 7, 2021): @hellish Thank you for opening this issue! Would you mind explaining the reason you need this feature in detail, so that I can understand the use case. It shouldn't be too difficult to add this feature, but I'm not 100% convinced that we need to support this.
Author
Owner

@hibiken commented on GitHub (Mar 11, 2021):

Closing this for now. @hellish feel free to reopen the issue if this is still something that you're interested in.

<!-- gh-comment-id:796404689 --> @hibiken commented on GitHub (Mar 11, 2021): Closing this for now. @hellish feel free to reopen the issue if this is still something that you're interested in.
Author
Owner

@zdraganov commented on GitHub (Sep 3, 2021):

In detail, you can use the same Redis instance for multiple services that are running asynq. If so, we want to have separate redis entries for each of the service, so we can have payment_asynq:... , order_asynq:... as any of those will be in the scope of the service itself.

<!-- gh-comment-id:912489381 --> @zdraganov commented on GitHub (Sep 3, 2021): In detail, you can use the same Redis instance for multiple services that are running asynq. If so, we want to have separate redis entries for each of the service, so we can have `payment_asynq:...` , `order_asynq:...` as any of those will be in the scope of the service itself.
Author
Owner

@hibiken commented on GitHub (Sep 5, 2021):

@zdraganov thank you for the comment.
Can we achieve that with custom queue names?
For example, you can create payment related queues such as "payment:foo", "payment:bar", etc
and create order related queues such as "order:baz", "order:qux", etc.

<!-- gh-comment-id:913081472 --> @hibiken commented on GitHub (Sep 5, 2021): @zdraganov thank you for the comment. Can we achieve that with custom queue names? For example, you can create payment related queues such as `"payment:foo"`, `"payment:bar"`, etc and create order related queues such as `"order:baz"`, `"order:qux"`, etc.
Author
Owner

@gurupras commented on GitHub (Nov 5, 2022):

One neat way in which a prefix would help is to be able to host multiple isolated asynq-based worker pools within one redis server.

<!-- gh-comment-id:1304548384 --> @gurupras commented on GitHub (Nov 5, 2022): One neat way in which a prefix would help is to be able to host multiple isolated asynq-based worker pools within one redis server.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asynq#85
No description provided.