The discussion revolves around the minimum Redis version requirement for Discourse, which is set at v6.0 despite Sidekiq only requiring v4.0+. andyv1 questions the rationale, noting Google Cloud Redis only supports v5. Falco explains that v6.0 is the version tested and used in production, and while older versions may work, they aren’t supported. Falco elaborates that Discourse uses Redis for multiple purposes beyond Sidekiq, including live updates via the message_bus gem, Rails cache, rate limiting, and semaphores. andyv1 seeks more details on Redis usage, and pfaffman shares that they’re using Google Cloud Redis but plan to migrate to AWS, suggesting potential compatibility concerns with managed services.
That is the version we test and use in production in our hosting.
You may do your own due diligence and evaluate if it works with a previous version, but we don’t promise it will keep working with anything older than the version we recommend.
We use Redis for a lot more than Sidekiq.
That all said, the Redis feature set is pretty stable so it will probably work just okay today. But then you are on the hook testing upgrades carefully.
I’m running a deployment on GCP kubernetes, for just a bit longer. If I weren’t planning to move it to aws (it’s what the client wanted for an unrelated reason) I would probably switch to running my own redis and not use the Google one.