[solatic]

Can someone ELI5 where this is going to be valuable?

If you set up Postgres read replicas, make sure your queries are covered by appropriate indexes, and your hot queries are handled by Postgres from RAM anyway - do you really need a separate Redis cache?

I feel like anytime I'm going to pull in Redis for a cache, it's going to be for data that I'm not interested in having guaranteed persistency for, like session tokens, and so it'll be for data that I wouldn't be storing in Postgres anyway?

[lotharcable]

Probably useful for sharing stuff with services that already have access to redis, but you don't want to add SQL client dependencies for and/or don't want to give access to your database.

But you want to be able to store/have single source of authority and update them using a SQL database.

This would then eliminate the need to maintain a separate lambda or cron job or something like that to keep them in sync.

[vijaymohan1979]

https://github.com/redfly-ai-org/redfly.ai/wiki/Q-&-A