Redis Cache Layer
|Updated||November 11, 2014|
|Compatible||[3.0, 3.0se, 3.0ee, 3.0ep]|
|Description||This plugin overrides the internal dotcms caching infrastructure (Guava) and replaces it with Redis, an external caching server that can be independently networked and scaled.|
The plugin can be downloaded on github.com:
This static (not osgi) plugin will override the internal dotcms caching infrastructure (Guava) and replace it with redis, an external caching mechanism. This plugin is provided "as is" and any implementation of it should go through extensive testing before using it in a production environment.
The benefits of redis are multiple:
Redis needs to be configured externally to dotcms and there is a lot to learn in running a Redis server. For more information, see: http://Redis.io
You point to a redis server/port by using the dotmarketing-config.properties
Hopefully, the config is self documenting.
You can specify different servers to read from and to write to. This allows you to set up Redis in a master / slave configuration and write to the master and read from a slave.
To test, fire up a redis server locally, on port 6379 (should be the default):
The library used in this implementation is called Jedis. Jedis uses a configurable pool of connections to access the Redis server.