Currently, we don't support other message brokers other than Redis. Related feature request #173
But given that AWS MemoryDB is Redis compatible this may be easier to add support for.

If you don't mind, would you mind sharing why you'd use AWS MemoryDB instead of Redis?

@hibiken commented on GitHub (Apr 8, 2022): @rohitjha941 Thank you for the question! Currently, we don't support other message brokers other than Redis. Related feature request #173 But given that AWS MemoryDB is Redis compatible this may be easier to add support for. If you don't mind, would you mind sharing why you'd use AWS MemoryDB instead of Redis?

kerem commented

2026-03-15 19:44:39 +03:00

Author

Owner

@rohitjha941 commented on GitHub (Apr 10, 2022):

I was thinking about using memory DB as it persists data during shutdown/failover and it is cheaper than running a managed Redis instance with failover.

@rohitjha941 commented on GitHub (Apr 10, 2022): I was thinking about using memory DB as it persists data during shutdown/failover and it is cheaper than running a managed Redis instance with failover.

kerem commented

2026-03-15 19:44:45 +03:00

Author

Owner

@hibiken commented on GitHub (Apr 11, 2022):

Makes sense. I'll look into this when I work on #173

@hibiken commented on GitHub (Apr 11, 2022): Makes sense. I'll look into this when I work on #173

kerem commented

2026-03-15 19:44:50 +03:00

Author

Owner

@sudslab commented on GitHub (Jan 8, 2023):

Any update on this? We are currently deployed in AWS - would be great to use a managed-cluster vs running our own on k8s. Thanks!

@sudslab commented on GitHub (Jan 8, 2023): Any update on this? We are currently deployed in AWS - would be great to use a managed-cluster vs running our own on k8s. Thanks!

kerem commented

2026-03-15 19:44:55 +03:00

Author

Owner

@chayim commented on GitHub (Feb 15, 2023):

@sudslab instead of memorydb have you thought about just using Redis Cloud? You don't have to handle any of the clustering, and get the same features?

@chayim commented on GitHub (Feb 15, 2023): @sudslab instead of memorydb have you thought about just using Redis Cloud? You don't have to handle any of the clustering, and get the same features?

kerem commented

2026-03-15 19:45:00 +03:00

Author

Owner

@abit2 commented on GitHub (Oct 1, 2024):

Tried using memorydb cluster.

Failed to forward scheduled tasks: INTERNAL_ERROR: INTERNAL_ERROR: redis eval error: dial tcp xx.xxx.xxx.xx:6379: i/o timeout

Seems similar to this. https://github.com/redis/go-redis/issues/2046

@abit2 commented on GitHub (Oct 1, 2024): Tried using memorydb cluster. ``` Failed to forward scheduled tasks: INTERNAL_ERROR: INTERNAL_ERROR: redis eval error: dial tcp xx.xxx.xxx.xx:6379: i/o timeout ``` Seems similar to this. https://github.com/redis/go-redis/issues/2046

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#2220

No description provided.

Rows
Columns