New in Symfony 4.4: Redis Cache Improvements
Redis is a popular in-memory data structure store which is used as a database, a cache and a message broker. Redis is also one of the most popular adapters of the Symfony Cache component and we've improved it in Symfony 4.4 with new features.
Redis Sentinel is a distributed system that provides high availability for Redis. It allows you to create a Redis deployment that resists certain kinds of failures without human intervention.
In Symfony 4.4, we've added support for it thanks to the new
option that you can add to the Redis connection DSN:
1 2 3 4 5 6
use Symfony\Component\Cache\Adapter\RedisAdapter; // set the 'redis_sentinel' parameter to the name of your service group $client = RedisAdapter::createConnection( 'redis:?host[redis1:26379]&host[redis2:26379]&host[redis3:26379]&redis_sentinel=mymaster' );
That's all! The only caveat is that Sentinel also requires the Predis library.
Tag Aware Adapters are used in Symfony Cache to invalidate caches based on
tags instead of expiration time. In Symfony 4.4 we've improved the
in several ways:
- We've lowered the Redis requirement to 2.8 and we no longer require certain
- We've raised the 2 billion keys per tag constraint to 4 billion keys per tag, which is the limit of the Redis Set datatype;
- We've improved the invalidation process to also delete the tag key in order to avoid leaving unused tags that gradually consume more and more memory;
- We've made the delete operations faster by reducing them to a single round-trip instead of two.
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.