phpredis VS Predis

In the next section we're going to configure redis bundle to use phpredis library. Install it before continuing

And then, read up on the PHPRedis Extension to see how easy it is to use -> https://github.com/phpredis/phpredis

I typically use Redis for all stores (queues, sessions and cache) and I don't have problems like that. It should be comparable to memcached in terms of speed, if that's something that might concern your app. You can find the installation instructions here. After installing redis itself and the PHP extension, you can just switch from 'memcached' to 'redis' in config/sessions.php[driver].

I've done this using PHP/Redis and EventSource, it's a viable option if you don't want to depend on an outside service. The php-redis extension has built in pub/sub capabilities so it's like 30 lines of code to get something up and running quickly.

I am going to connect to redis using the libary predis. Simply add the following to your compose.json

Personally, I prefer Redis for caching. I find it simple and intuitive to work with, using Predis as the connecting client.

That looks like you're connecting to a redis cluster running in cluster mode. The message is directing your client to retry its query on a different shard. You typically need to connect to those using a client/library that is cluster aware. I am not experienced with PHP, but this looks like an option.