[GH-ISSUE #863] Add example for redict.io and NATS jetstream #424

Closed
opened 2026-03-02 05:21:07 +03:00 by kerem · 1 comment
Owner

Originally created by @kharabela on GitHub (Apr 16, 2024).
Original GitHub issue: https://github.com/hibiken/asynq/issues/863

Originally assigned to: @hibiken on GitHub.

With recent redis license change.I feel there is need to add usage guidance for redict.io and NATS jetstream or postgressql. Please help me to understand if I want to replace redis with redict.io or NATS Jetstream or postgresql what changes do I need to make

Originally created by @kharabela on GitHub (Apr 16, 2024). Original GitHub issue: https://github.com/hibiken/asynq/issues/863 Originally assigned to: @hibiken on GitHub. With recent redis license change.I feel there is need to add usage guidance for redict.io and NATS jetstream or postgressql. Please help me to understand if I want to replace redis with redict.io or NATS Jetstream or postgresql what changes do I need to make
kerem 2026-03-02 05:21:07 +03:00
  • closed this issue
  • added the
    wontfix
    label
Author
Owner

@kamikazechaser commented on GitHub (Apr 16, 2024):

This library is tightly coupled with Redis. Only a pure Redis drop-in replacement will work. Both ValKey and Redict.io should work out of the box.

<!-- gh-comment-id:2058249590 --> @kamikazechaser commented on GitHub (Apr 16, 2024): This library is tightly coupled with Redis. Only a pure Redis drop-in replacement will work. Both ValKey and Redict.io should work out of the box.
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#424
No description provided.