[Question] Will this work with AWS MemoryDB ?

[rohitjha941]

No description provided.

[hibiken]

@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?

[rohitjha941]

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.

[hibiken]

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

[sudslab]

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!

[chayim]

@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?

[abit2]

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. redis/go-redis#2046