We use a vendor to host and mange the Redis and PostgreSQL clusters utilised by our ChirpStack (v4.8.1) instance (which run on AWS EC2).
A licence change for Redis seems to indicate that Redis’ enthusiasm for other companies to offer hosted versions of the open source version (rather than use Redis’ own cloud hosted offering) means that such vendors seem to be planning an exit from offering a hosted Redis version and are looking more towards using similar products (potentially more modern with increased performance and drop-in replacements for Redis), such as Dragonfly (https://www.dragonflydb.io).
While not an immediate concern for us as vendors continue to host Redis (just with a modified product name, at least for now) and we could just switch to using the Redis cloud offering (although this has a noticeable price increase) I was wondering if anyone had a view on if ChirpStack is likely to support another caching solution (as I see that PostgresSQL is now not the only database option) or if anyone had tested ChirpStack using Dragonfly or similar?
I’m keeping an eye on this. The most likely alternative would be migrating over to https://valkey.io/, which is a fork created at the time Redis changed its license. I believe it would be a drop-in-replacement for Redis, although they are slowly adding new features that are different from Redis.
This makes total sense; Valkey and Dragonfly were the options that magically appeared on the vendor’s platform after the licence change for Redis.
It is likely that I will now look to use one of the above for data caching in my systems (outside of ChirpStack); I’d be happy to Beta test any proposed migration should you decide to move, or offer another option, at any point.
Dragonfly claims to be a drop-in replacement, Valkey is a fork of Redis before the license-change thus should be a drop-in replacement too. Thus for testing one of these replacements there should be no changes required from the ChirpStack side.