I'm doing research on use-cases of #Redis® or #valkey. And how developers are using those in their applications. Boost for more reach would be very nice.

#php #research

cache
53.5%
persistent storage
6.9%
queue
32.7%
other please 🧵👇
6.9%
Poll ended at .
Thanks to everyone who responded. This was very helpful🫶
@jaapio Session clustering.
@mwop to be able to share sessions over multiple application servers I assume. So Redis is also high available in your case?
@jaapio Correct - allows multiple php pools to share session state, for horizontal scalability. Generally more performance than using a relational database.
@mwop thanks, for these insights. This is how I thought many people would use Redis.
@mwop @jaapio Hm.... I filed that under "caching".....
@jaapio I wrote a simple distributed processing framework based on Redis - https://wiki.tcl-lang.org/page/DisTcl .
DisTcl - Distributed Programming Infrastructure for Tcl

Tclers wiki

@CGM why Redis for this? Would a queue like RabbitMQ not be a better fit? If I understand the snippet on your link correctly you do use key value collections to distribute jobs? So not the pub/sub feature of Redis
@jaapio I've not looked at RabbitMQ in detail, but I don't think it would provide the caching of results which I get from Redis.
To distribute jobs I use rpush/blpop on lists, this ensures that each job gets picked up by a single server, which I don't think would be the case for pub/sub.
I use this system quite heavily in newsgrouper.org, my web/usenet gateway, which I gave a talk about recently: https://learn.wu.ac.at/eurotcl2025/lecturecasts/753988250?m=delivery
Lecturecasts - Day 1 - Newsgrouper, a Tcl-powered web interface to Usenet (Colin Macleod)

@CGM thanks for sharing. This is really helpful
@jaapio I work with Adobe Commerce, which uses Redis for cache and session storage, and RabbitMQ for queuing.

@jaapio Apart from Session storage (as @mwop already wrote) it's also an awesome Projection Storage. To me, that's somewhere in the middle between cache and persistent storage: It's not a cache, as the code in question doesn't have a fallback to "fix" a miss. But it's also not persistent because in-memory.

I've been suggesting that as a lightning fast means to serve html content since like forever ;) #php

@theseer are you using it with persistent settings? Redis can write to disk as well, which has a small performance penalty
@jaapio I usually do not. But I know people who opted for that. I usually do no see the point because I have replica in case one goes down.

@jaapio Late to the party. Big fan of redis for Session Storage, Cache and Queues.

Why? Redis is simple to host and deploy, does not take lot of resources works great if configured correctly for the different usecases.

A Redis for Cache should not be the same as the Redis for Queue as it should be configured differently.