Comments

If using it purely as cache layer, there isn't a much advantage over other cache layers. If redis is used as a data structure server it is then it has an advantage, but that it quite a big change in architecture.

It seems that Redis can basically replace Memcached entirely in practice because it's more robust and actively developed, while having more functionality and still being able to do the same thing. Notable advantages it has over Memcached includes more advanced data type support, built-in clustering functionality (supported by the developers), and persistence to disk.

It would be great to see an implementation for Redis used at least as a cache layer, or even used in some parts of the framework as a data structure server as we move forward to allow us to improve scalability, but for now Memcached works just as well for what it's currently being used for in Garden.

Just making this post to see if anyone has any experience with Redis and what other benefits implementing it may bring to the table for Garden.

Nothing on this since Feb so I'm going to pick it up. Been looking at dropping memcached at work in favour of Redis storage for sessions so will tan it out while its still fresh.

Looking at the class.cache.php it really shouldn't take too long it's just when I had time to actually do it... I'll post patch/PR whatever here when I have something worth sharing and then if people could test that would be cool.

We'd be interested in seeing a pull request or issue collaboration about this. I know @initvector has expressed interest in adding Redis support so perhaps mention him on GitHub (same username) if you do.