What is the difference between the different variants of Redis?


I know there are different alternatives to use Redis in Fly, namely the one indicated in the documentation, KeyDB and Geo Redis Cache, from what I saw on Fly’s GitHub.

Which one do you recommend to use and in which context?

For example, for caching, action cable / any cable, storing simple values, etc.


I would use vanilla Redis for almost everything.

The geo redis setup is useful for regional caching and storing simple values to read later. Action Cable needs to share the same redis instance or it can’t do it’s thing. Sidekiq and similar also need a single primary Redis.


And what is the advantage of using KeyDB as shown in the Rails example with Anycable?

I ask because that generated me a bit of confusion

KeyDB has a neat master<->master ability. It doesn’t work as well as we want in practice, though.

If all goes well, we’ll have a fully managed ready-to-go Redis option available in a month or three.

1 Like

Oh, great, glad to hear that!
I’m very happy to switch to Fly.
I was on Digitalocean App Platform before, tried Render and Railway, and you guys are the best! Keep it up